nyuuzyou/wikis huggingface dataset:
Attending a Live Performance

== Support Live Performance!!! ==
Many people put in a lot of time, effort and real money into making Second Life a vibrant performing arts environment. Consider tipping performers *and* venues, both to let them know that they are of value to you, and to help them defray their costs so that they are there for you in the future!
== Communicating With Performers ==
Performers in Second Life run a viewer, and watch their screen to see the chat and im's sent to them during the performance. This allows the performer to "hear" your comments in a way is very different than in a traditional live performance, and enables them to interact with the audience in a more direct way. Performers will often choose to talk back (using voice) to audience comments sent in chat or IM.
== Stream Delay ==
Because of the way streaming works in general on the Internet, there is a very real delay between the music or sound sent by a performer, and the time that it shows up in Second Life. This delay is often about 10-20 seconds. What does this mean to you as an audience member? When you chat or IM to a performer, and expect a response, understand that if they talk back to you it will be a while after you send the IM, and that does not mean that they're not paying attention to you - it just takes a bit for you to hear what they said!
== Typing Sounds And How To Suppress Them ==
In Second Life, there is a standard "typing sound" added when you are typing in open chat. This can be disruptive to live performances, so most performers and performance venues expect you to type with the typing sounds disabled. You can do this in two main ways:
* Start each line of open chat with "/", such as "/That was great!"
* Start each line with "/0", which does not display the "/" character
You can also use a Debug Setting to suppress the typing sound without having to type "/". For more info, see "How to turn off the typing animation and sound".
Austria Microcontinent

Austria is a Microcontinent located inside Grid Sector K13, at Coordinates 1104-1110/1382-1388. It is placed inside Eastern Ocean and has the temporary name A055 given by Second Life Geography team. It is an isolated microcontinent and in the same time a Sim Cluster since there are a few distant sims, linked economically to the microcontinent. Name is not official and comes from the fact that the Western sims have Austrian names, but the Eastern sims share German names.
The microcontinent is formed of 17 sims, while 6 other remote sims can be found nearby, forming a Sim Group.
== Geography ==
This microcontinent can be divided into 3 main regions:
Urban Land is on plain, full of urban buildings and squares, like in Munich City.
Rural Land is usually mountain land (low mountains or high hills). It cah be found in sims like Goethe. There are rivers and forests.
Snowlands can be found in West part of the microcontinent, where ground has an incredible declivity. Altitude rises up to 130 meters, higher then many continents.
== Transportation ==
There is a lrge network of roads, one that would envy people on many continents. The road network is doubled by paths. Very important is the presence of the German Railway, that connects 10 sims and has even an underground sector. In West, there are even other snowland transportation devices.
== See Also ==
Second Life Geography
List Of Microcontinents And Sim Clusters
Authenticated Chat

Here's a method of authenticating chat with shared secret.
//By: Gigs Taggart
//Modified by Strife Onizuka
//Released under BSD license
string gSetupNotecardName = "setup";
string gPassword;
integer gSeed;
key gSetupQueryId;
integer gSetupNotecardLine;
//to sign a message we hash message+gSecret+llGetKey()
string sign_message(string message)
{
 string hash = llMD5String(message + gPassword + (string)llGetKey(), gSeed);
 return message + hash;
}
//to verify a message we do all the same stuff except we get the sender's key
integer verify_message(string raw, key sender)
{
 string hash = llMD5String(llDeleteSubString(message, -32, -1) + gPassword + (string)sender, gSeed);
 return llGetSubString(message, -32, -1) == hash;
}
readSettingsNotecard()
{
 gSetupNotecardLine = 0;
 gSetupQueryId = llGetNotecardLine(gSetupNotecardName, gSetupNotecardLine); 
}
default
{
 state_entry()
 {
 readSettingsNotecard();
 }
 dataserver(key queryId, string data)
 {
 if(queryId == gSetupQueryId) 
 {
 if(data != EOF)
 {
 integer split = llSubStringIndex(data, "=");
 if(~split)
 {
 string setting = llDeleteSubString(data, split, -1);
 string value = llDeleteSubString(data, 0, split);
 if (setting == "password")
 {
 gPassword = value;
 }
 else if(setting == "seed")
 {
 gSeed = (integer)value;
 }
 }
 gSetupQueryId = llGetNotecardLine(gSetupNotecardName, ++gSetupNotecardLine); 
 }
 else
 {
 state running; 
 }
 }
 } 
 changed(integer change)
 {
 llResetScript();
 }
}
state running
{
 changed(integer change)
 {
 llResetScript();
 }
}
====Notecard====
Name: "setup"
password=secret
seed=0xdeadbeef
Authentication Flow

== Protocol Step-by-step ==
=== Step 1 ===
Viewer(client)--------->User Server
* Secure Message checksum request - Protocol Level Supported? Yes/No.
* Port 12036
=== Step 2 ===
Viewer -----------> Login Server
* XML-RPC Func call - over HTTPS. to login. (Blocking) [[Login Info from libsecondlife]
* Mostly a web server (Apache) that talks to a SQL DB. Gets user info from DB (home. etc.) gets the info about which sim to connect to (IP address etc.) and drops the connection.
* First name, last name, MD5(password), viewer version, requested location
=== Step 3 ===
Login Server ------> Database
Checks actual database for authentication credentials
=== Step 4 ===
Login Server------> SIM in the Grid
* Login server decides which SIM to send the viewer to. talks to Grid 
* Requests session start
Grid (of Simulators):
* inbound UDP port (for comm. with Viewer) 12035, 13000-13050
=== Step 5 === 
SIM ----> Login server (response)
* Verification that user is allowed on the SIM
=== Step 6 ===
Login server ------> Viewer (response)
* Information returned: agent id, session id, secure session id, sim ip, sim port, global location, some inventory info.
* Most IDs are UUIDs (agent id, session id, and secure session id, for example)
* Agent ID == User ID Unique and Persistent.
=== Step 7 ===
Viewer -------> Simulator (on Grid)
Handshake 
* Viewer sends user id and session id
=== Step 8 ===
Viewer -------> User server
User server handshake
* Sent for presence information so Group IM works 
* Confers group rights to user
* User server verifies the SIM session info via DB Presence-Agent table.(initially committed by the Login Server at the time of Sim-LoginSERVER negotiation) Step p3
Category: AW Groupies
Autobuild/Adding Dependencies

Here are some examples for how to add and update installables for dependency packages. It's a work in progress.
This picks up where Autobuild/Quick_Start left off.
Example from this build:
 autobuild installables add expat platform=windows url=http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/3p-expat/rev/221208/arch/CYGWIN/installer/expat-2.0.1-windows-20110215.tar.bz2 hash=e72db1bda49b205ebdf4945d4ed2b8f8
 autobuild installables edit expat platform=linux url=http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/3p-expat/rev/221208/arch/Linux/installer/expat-2.0.1-linux-20110215.tar.bz2 hash=750a6f119f828ba464029b7584acfc79
 autobuild installables edit expat platform=darwin url=http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/3p-expat/rev/221208/arch/Darwin/installer/expat-2.0.1-darwin-20110215.tar.bz2 hash=a9fdcc2afc0a7f9711e28530f098e402
Autobuild/Cygwin

Previously, Windows users with a "native" Python install were advised to avoid the Cygwin shell like the plague.
However, things should be better now. We are now using the distribute extension of the python setuptools, so the autobuild application installed should now be equally executable by any shell.
If you want to run autobuild directly from a mercurial checkout without installing, we still provide the autobuild.cmd wrapper. It can be used by executing the following:
 ln -s /path/to/autobuild/checkout/bin/autobuild.cmd ~/bin/autobuild
 export PATH="$PATH:~/bin/"
or by adding /path/to/autobuild/checkout/bin to your windows PATH.
However, as this is trickier to set up and more error prone, it is not the primary method that we recommend in Autobuild#Getting_Autobuild.
Autobuild/Integration

This page describes how to make changes to Autobuild and get it tested and integrated for others to use. It's intended to be analogous to the process described at How To Submit A Viewer Change but somewhat simplified.
== Testing Requirements ==
=== Unit Tests ===
Tests are under autobuild/tests
You can run them by running nosetests -v from the top of the autobuild source tree. (see nose documentation) 
=== Integration Tests ===
We have teamcity running a test build against a staging repo: autobuild-integration. So changes should be pushed there first for testing before getting promoted to http://bitbucket.org/lindenlab/autobuild .
You need to check out 4 repos side-by-side to run the tests here:
*buildscripts (note this is currently broken, as default-autobuild.sh is missing for now)
*autobuild (cloned from your branch with your new changes to test)
*autobuild-testscript
*3p-curl
Then run autobuild-testscript/build.sh. You can also test against additional packages by checking them out alongside 3p-curl and setting the test_pkgs environment variable either manually or in autobuild-testscript/BuildParams
Autobuild/Lexicon

This document defines terms as they are used in the context of Autobuild. This is not design documentation, but rather a resource to help define key phrases and words we use.
; Archive
: A file containing a set of artifacts used to store and transport dependencies from source builds to dependent builds.
; Artifact
: One or more files from a package that can be dependencies of another build. Some artifacts are the output of the build of a package, like a static library, dll or an executable. Some artifacts can be source for a package that needs to be redistributed, like header files that define symbols in a build.
; Autobuild
: Autobuild is the name of the tool. It is a command line tool supported on Windows, MacOS, and Linux. It is useable by developers and scripts to ease building and maintaining projects from multiple modular sources.
; Build Configuration
: A named configuration variant specifically for configuring or building package source. In particular a build configuration selects sets of options to pass to the configuration and compiler executables.
; Build Id
: A unique number for the build provided by the --id option to the build subcommand; defaults to a date/time stamp
; Build-time Dependency
: A file needed by a build for successful completion. Some artifacts, like header files, are build time dependencies.
; Configuration
: A superset of all parameters affecting a build of a given version. The package will need to describe which artifacts are specific to which configurations for downstream builds. config info: Platform, Compiler, Build Variant, CPU architecture.
; Package
: Metadata that describes the dependencies, artifacts and supported configuration info for a build. The sharing the metadata allows dependent builds to use the artifacts. The metadata should also describe how to start with a source version and produce expected artifacts from a build.
; Package Repository
: A database containing info about available packages and the URLs for finding their versions and artifacts.
; Run-time Dependency
: A file needed by a build to execute its output. Some artifacts, like dlls, are run time dependencies and will need to be redistributed with the output of a dependent build. Artifacts can be both run-time and build-time dependencies. Its up to the dependent build to determine.
; Source Repository
: A location containing the source for a project. The source repository format is not specified, it could be an hg repository or a tarball, etc.
; Version
: A unique and reproducible set of source data for a package.
; Working Copy
: The location where a source is being built. A developer will create a local working copy of source and a package to do development. The artifacts for the working copies dependencies will be copied into the working copies build folder.
; Working Platform
: The platform under which the autobuild tool is invoked, e.g. 'darwin' when running an autobuild tool on a Mac running OS X.
Category:Autobuild Category:Open Source Portal
Autobuild/Package Layout

__TOC__	Autobuild does not place much in the way of restrictions on how a package is bundled into an archive. The autobuild package command will simply create an archive from the build directory gathering all the files which match manifest entries. When that package is installed using autobuild install, it is just expanded into the packages subdirectory of the build directory. That said, there is a recommended layout of various build products which has (mostly) been followed by Linden apps. On this page we give the details of that recommended layout.
=== Package layout ===
The basic layout for a typical package archive is:
*bin
*include
**include/<packagename>
*lib
**lib/debug
**lib/relwithdebinfo
**lib/release
*LICENSES
==== binaries ====
Package executables in the bin directory of the archive.
==== headers ====
Package header files in the include directory of the archive typically in a subdirectory named after the package. For example one might include the header foo.h" for the foo package in include/foo/foo.h.
==== libraries ====
Package static and shared libraries in the lib directory in a subdirectory which matches the build configuration (all lower case). This is especially important for packages built for windows where debug and release libraries are binary incompatible. As an example, if the foo package produces a library foo.lib, the version built with debugging enabled should be bundled in lib/debug whereas the optimized version should be bundled in lib/release.
==== License files ====
Include a copy of the package's license in the LICENSES directory. By convention, license files are named packagename.txt.
=== Gotchas ===
*Some existing packages have their libraries located directly under lib, some have them under lib/{debug,relwithdebinfo,release}
*Python packages are not fully supported, as we have not determined how to cleanly organize python module directories for compatibility with multiple python versions
Category:Autobuild Category:Open Source Portal
Autobuild/Quick Start/Build Configured

{'package_description': {'copyright': 'Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>',
 'description': u'The GNU Hello program produces a familiar, friendly greeting. Yes, this is another implementation of the classic program that prints \u201cHello, world!\u201d when you run it.',
 'license': 'gpl3',
 'license_file': 'LICENSES/hello.txt',
 'name': 'hello',
 'platforms': {'common': {'configurations': {'default': {'build': {'command': '../build-cmd.sh'},
 'name': 'default'}},
 'name': 'common'},
 'darwin': {'build_directory': 'stage',
 'configurations': {'default': {'build': {},
 'default': 'true',
 'name': 'default'}},
 'name': 'darwin'},
 'linux': {'build_directory': 'stage',
 'configurations': {'default': {'build': {},
 'default': 'true',
 'name': 'default'}},
 'name': 'linux'},
 'windows': {'build_directory': 'stage',
 'configurations': {'default': {'build': {},
 'default': 'true',
 'name': 'default'}},
 'name': 'windows'}},
 'version': '2.6'},
 'type': 'autobuild',
 'version': '1.2'}
Category:Open Source Portal
Autobuild/Quick Start/Manifest Configured

{'package_description': {'copyright': 'Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>',
 'description': u'The GNU Hello program produces a familiar, friendly greeting. Yes, this is another implementation of the classic program that prints \u201cHello, world!\u201d when you run it.',
 'license': 'gpl3',
 'license_file': 'LICENSES/hello.txt',
 'name': 'hello',
 'platforms': {'common': {'configurations': {'default': {'build': {'command': '../build-cmd.sh'},
 'name': 'default'}},
 'manifest': ['include/hello/*.h',
 'LICENSES/hello.txt'],
 'name': 'common'},
 'darwin': {'build_directory': 'stage',
 'configurations': {'default': {'build': {},
 'default': 'true',
 'name': 'default'}},
 'manifest': ['lib/*.a',
 'bin/*'],
 'name': 'darwin'},
 'linux': {'build_directory': 'stage',
 'configurations': {'default': {'build': {},
 'default': 'true',
 'name': 'default'}},
 'manifest': ['lib/*.a',
 'bin/*'],
 'name': 'linux'},
 'windows': {'build_directory': 'stage',
 'configurations': {'default': {'build': {},
 'default': 'true',
 'name': 'default'}},
 'manifest': ['lib/debug/*.pdb',
 'lib/release/*.pdb',
 'lib/release/*.lib',
 'lib/debug/*.lib',
 'bin/*.exe'],
 'name': 'windows'}},
 'version': '2.6'},
 'type': 'autobuild',
 'version': '1.2'}
Category:Open Source Portal
Autobuild/Quick Start/build-cmd.sh

#!/bin/bash
# turn on verbose debugging output for parabuild logs.
set -x
# make errors fatal
set -e
if [ -z "$AUTOBUILD" ] ; then 
 fail
fi
if [ "$OSTYPE" = "cygwin" ] ; then
 export AUTOBUILD="$(cygpath -u $AUTOBUILD)"
fi
HELLO_VERSION="2.6"
HELLO_SOURCE_DIR="hello-$HELLO_VERSION"
HELLO_ARCHIVE="hello-$HELLO_VERSION.tar.gz"
HELLO_URL="http://ftp.gnu.org/gnu/hello/$HELLO_ARCHIVE"
HELLO_MD5="066ba7113eed3554cde6bc34b7b43e9b" # for hello-2.6.tar.gz
# load autbuild provided shell functions and variables
eval "$("$AUTOBUILD" source_environment)"
fetch_archive "$HELLO_URL" "$HELLO_ARCHIVE" "$HELLO_MD5"
extract "$HELLO_ARCHIVE"
top="$(cd $(dirname $0) ; pwd)"
stage="$(pwd)"
pushd "$HELLO_SOURCE_DIR"
 case "$AUTOBUILD_PLATFORM" in
 "windows")
 fail "GNU hello doesn't really build on windows. I guess I chose a bad example, sorry! -Brad"
 ;;
 "darwin")
 opts='-arch i386 -iwithsysroot /Developer/SDKs/MacOSX10.4u.sdk'
 CFLAGS="$opts" CXXFLAGS="$opts" ./configure --prefix="$stage"
 make
 make install
 ;;
 "linux")
 # TODO: see darwin notes here above
 CFLAGS=-m32 CXXFLAGS=-m32 CC=gcc-4.1 CXX=g++-4.1 ./configure --prefix="$stage"
 make
 make install
 ;;
 esac
 mkdir -p "$stage/LICENSES"
 cp COPYING "$stage/LICENSES/hello.txt"
popd
pass
Category:Open Source Portal
Autobuild Shell Functions

You can install autobuild 1.0 (e.g. into a virtualenv) from the alternate repository using a command such as (bash):
 pip install 'hg+http://bitbucket.org/lindenlab/autobuild-1.0#egg=autobuild'
or (Windows command prompt):
 pip install hg+http://bitbucket.org/lindenlab/autobuild-1.0#egg=autobuild
Autobuild offers a set of shell functions for use in build-cmd.sh scripts which can be added to the environment by inserting lines such as the following into your build script:
if [ "$OSTYPE" == "cygwin" ]
then autobuild="$(cygpath -u "$AUTOBUILD")"
else autobuild="$AUTOBUILD"
fi
eval "$("$autobuild" source_environment)"
When invoking autobuild from within your build-cmd.sh, you must convert it to cygwin syntax so that cygwin bash doesn't get confused. However, it is essential to avoid overwriting the AUTOBUILD environment variable itself, or various child programs will, in turn, be confused. Capture the converted autobuild pathname in a different environment variable local to your script. Since bash environment variables are case-sensitive, it works to use autobuild for the cygwin-form path, leaving AUTOBUILD for the native-form path.
The exact shell code that is injected into your environment upon execution of this command is here, with (for Windows) additional functions here.
== General functions ==
Shell functions provided by autobuild:
Function 	Description
pass 	Indicates build has succeeded
fail $comment 	Indicates build has failed, citing $comment in the output
fetch_archive $url $archive $md5	Uses curl to download $archive from the $url and checks the downloaded file hash against the $md5 provided.
extract $file 	Extracts contents of an archive appropriate for the tar extension of $file.
calc_md5 $file 	Calculate the md5 of $file
== Windows-only commands ==
Windows-only shell commands (Cygwin):
Function 	Description
build_vcproj $vcproj $config 	Launches a Visual Studio build of $vcproj, building configuration $config. 
If $USE_INCREDIBUILD is set, the same build is launched via BuildConsole, Incredibuild's command-line launcher.
build_sln $sln $config $project	Launches a Visual Studio build using the solution file $sln, configuration $config, and specifying project $project. 
If $project is omitted, then the entire solution will be built.
load_vsvars 	Import Visual Studio paths, includes and libs into the shell environment
Category:Autobuild
Autobuild build

Command-Specific Options
Option 	Shortcut 	Value 	Description
--all 	-a 	None 	Build all configurations
--config-file config-file	N/A 	Configuration file to use 	Build using the specified configuration file
--configuration config 	-c config	Configuration to use 	Build a specific build configuration
--no-configure 	N/A 	None 	by default, the build command runs configure before building; using this option prevents the reconfiguration
-- option 	N/A 	Option to pass, including leading dash	Pass specified option to the build command. Passed "as is," so don't forget the "-". Example:
-- -j1
--id build-id 	N/A 	A unique id for this build. 	Defaults to the AUTOBUILD_BUILD_ID environment variable if it exists and has a value, or to a date/time stamp if not (a warning is issued in this case).
--address-size bits 	N/A 	Either 32 or 64 	Defaults to the AUTOBUILD_ADDRSIZE environment variable if it exists and has a value, or to 32 if not.
Category:Autobuild
Autobuild configure

Command-Specific Options
Option 	Shortcut 	Value 	Description
--all 	-a 	None 	Build all configurations
--config-file config_file	N/A 	Configuration file 	Use specified configuration file. Defaults to $AUTOBUILD_CONFIG_FILE or autobuild.xml.
--configuration config 	-c config	Configuration(s) to build 	Build a specific build configuration (may be specified as comma separated values in $AUTOBUILD_CONFIGURATION)
-- option 	N/A 	Option to pass, including leading dash	Pass specified option to the configuration command. Passed "as is," so don't forget the "-". Example:
-- -DFMOD:BOOL=ON
--address-size bits 	N/A 	Either 32 or 64 	Defaults to the AUTOBUILD_ADDRSIZE environment variable if it exists and has a value, or to 32 if not.
Category:Autobuild
Autobuild edit

Command-Specific Options
Option 	Shortcut	Value 	Description
--delete 	N/A 	? 	
--config-file config_file	N/A 	Configuration file	Use specified configuration file
Arguments for build subcommand
* name - Name of config
*platform - Platform of config
*command - Command to execute
*options - Options for command
*arguments - Arguments for command
Arguments for package subcommand
*name - Name of package
*description - Package description
*copyright - Copyright string (as appropriate for your package)
*license - Type of license (as appropriate for your package)
*license_file - Path to license file relative to package root, if known
*version_file - Path to a file containing the package version number after the build 
Arguments for platform subcommand
*name - Name of platform
*build_directory - Build directory 
Category:Autobuild