nyuuzyou/wikis huggingface dataset:
Second life musician

My name is Seth Regan... at least it was until November of 2006 when it became Mankind Tracer. I have been a professional rock singer/guitarist touring for over 20 years. I stumbled across Second Life and decided to join. Once in, I started to notice there were live musicians, DJ's, poets and other artists performing. What I failed to realize at first was that they were performing to a global audience.
I coulnd't beleive it. I thought, well if they can, why can't I? So I learned all I could about SL "streaming" and before I knew it I had landed my first gig. This was incredible. I can actually perform live without leaving my home and even better was, I didn't have to lug around any gear. I had all the gear I needed right in my small home studio and of course the milk crates in my garage.
After over 225 shows in SL, I am now billed as Second Life's Premiere Rock Performer, a title I don't take lightly. I attribute this not to myself, but to all the many, many wonderful people I have met from all across the globe who have shown me that kindness is worldwide. My group, The Friends of Mankind now hovers around 1200 people. I have sold more CD's than I did touring in real life and continue to be shown appreciation for my original works. My hat goes off to all the amazing residents who attend my shows, buy my music and even buy my SL fan clothing from my little shop on The Cape.
Why did I write this page? Well, I just wanted to say thank you to Linden Labs for all they do. Mostly, for giving me a place to perform and for afording me the opportunities I wouldn't otherwise have had. It really is an amazing world we live in and an even more amazing Second Life.
I have only one request: over the past year, it has become increasingly difficult for me to perform anywhere without crashing the sims. This is due to the 100 agent limitation which I imagine is a server limitation. I am wondering if and when you guys might consider raising that limitation to 200.
Thanks a lot,
Mankind Tracer
AKA Seth Regan in RL
mankindtracer.com
Secondlife:// URL scheme

This wiki page answers the question, "How does the secondlife:// URL scheme work?"
For details on special secondlife:///app/ URLs that control the user interface for login and search, see Viewer URI Name Space
== Windows ==
The Second Life client utilizes the windows registry to tell the browser which application to launch when it sees secondlife:// as the prefix to a URL. During installation of the client, if the channel is "Second Life Release" (the default channel for the client) and the grid the client is installed for is "agni", the register entry is replaced with the path to the executable. The register entry states that whenever a browser sees secondlife:// that particular installation of the Second Life client is invoked with the arguments -url <URL>.
=== No Client is Running ===
When there is no client already running, the executed client will parse the -url argument and execute according to how it is parsed.
=== There is already a Client Running ===
The client looks to see if any applications running with the class name (specific to windows) "Second Life" is up. If so, it serializes the <URL> and sends it across the other client.
== Macintosh ==
The Mac client registers a GURL handler as soon as the Second Life Application is dragged from another volume onto your startup volume.
=== No Client is Running ===
That client will be launched and its GURL handler will handle the GURL event issued by the operating system.
=== There is already a Client Running and it's the GURL Client ===
The client will handle the GURL event
=== There is already a Client Running and it's *not* the GURL Client ===
The GURL client will be launched and it will fail with the message "Another instance of Second Life is running."
== Linux (SL 1.18.6+) ==
The Linux client (re-)registers secondlife:// handlers with GNOME and KDE each time it is launched.
=== No Client is Running ===
When there is no client already running, the executed client will parse the -url argument and execute according to how it is parsed.
=== There is already a Client Running ===
A warning will be issued - existing clients will currently need to be closed before a new external URL is handled.
Secondlife Monitoring

You want to know all about your Simulator(s) ?
Well, there is finally a solution :
* See the PrimUsage of all of your property
* See the Performance Data of all your Simulators
* See technical informations about your Simulators
* All easy to access and many useful hyperlinks to the SL-wiki...
* All Access is SSL-encryptet on a HTTPS-Host
* Fastest possible Web-Servers installed on Raid5-SSD Harddsiks
* No use of BOT´s, just rez 1Prim on your property, even nice for Mainland !
			
	
	
At the moment, this Service is still BETA and ANSI is working hard on new features !
NOTICE :
For now, the developing of this Service is on hold until LindenLabs is done with her Banning-Celebration.
While i not know if my Server-Connected-Resident´s will be banned (or not banned), i won´t work longer on this Scripts. Remember, i don´t use this Resident´s inworld as BOT, they are simply connected with Scripts (which need looooong developement and expensive time) between my Server and SecondLIFE.
see more at : 
https://secondlife.gehostet.de (Use the DEMO-Account : Name -> lookover / Password -> demo)
https://secondlife.gehostet.de/lang/de/secondlife-monitoring/
and/or buy a SIM-Monitoring directly at : 
https://marketplace.secondlife.com/p/ANSIs-Performance-PRIM/5274530
Ask ANSI Soderstrom inworld (just send a Notecard or InstantMessage)
SecuredTemplateChecksumRequest

==Message Layout==
{
	SecuredTemplateChecksumRequest Fixed 0xFFFFFFFA NotTrusted Unencoded
	{
		TokenBlock	Single
		{	Token	LLUUID	}
	}
}
==Usage and Notes==
Category:Messages
Category:Common Messages
This asks for a TemplateChecksumReply from the other node. It is used to ensure both nodes are using the same message template version.
Security Usecases

== Writing Usecases ==
These use case follow Alistair Cockburn's template. Note that there are several stages of usecase. If you want to grab a template for the early stage of a use case, you can get it here
== Firewall Realted Use Cases ==
===Use Case: Asset Security ===
Goal in Context:
 
Private assests owned by an avatar (identity) should not be identifiable or usable by any other avatars (identities) unless the avatar chooses to change the permission. Avatars should not lose control of these assets if they move to other regions. 
Scope:
 
Permisions on assests
Level:
 
Primary Task
Primary Actor:
 
avatar, asset, asset permission
Priority:
 
Protecting personal assests and their value is a very high priority.
Frequency:
 
Expected to happen frequently (every session).
----
===Use Case: Region Script Secruity ===
Goal in Context:
 
Regions should be able to control the execution of Scripts brought in by assets of avatars. For example, a secure region inside a firewall should be able to prevent scripts in rez'ed assets from listening to chat or scanning for other avatars. Basically, we need to prevent spying in secure regions.
Scope: 
 
avatar operating inside a "secure" region 
Level:
 
Primary Task
Prrimary Actor:
 
avatar inside a "secure" region such as behind a firewall.
Priority:
 
This is a priority for private regions where it is important to prevent the uncontroled outward flow of information. 
Frequency:
 
This is expected to be a key issue for organizations and corporations attempting to protect information.
----
===Use Case: Prevention of unauthorized Access ===
Goal in Context:
 
A secure region should be able to prevent unauthorized avatars (identities) from accessing or viewing a region. It should not be possible to "fake" the identity of a valid avatar.
Scope:
 
Avatar
Level:
 
Primary task
Primary Actor:
 
Avatar with invalid "identities" or faked "identities"
Priority:
 
This is a key requirement for any non-public region.
Frequency :
 
This will occur with any non-public region.
----
Security issues

Issues pertaining to the security of Second Life should be sent to Linden Lab via special mechanism described below. Please help us keep Second Life secure by ensuring that possible security exploits aren't broadly advertised before a fix is available.
So just what constitutes a security issue? If an issue poses any of the following threats to Second Life, its Residents or content, then it is an exploit and should be reported:
* exposes real life Resident identity without consent
* destroys content
* permits unauthorized access to Second Life/Linden Lab resources
* compromises a client or server host subjecting it to remote control
When reporting an exploit, please provide as much detail as possible, Including the environment used (e.g. Windows XP Service Pack 2, Nvidia 6800 etc ) and the complete reproduction case. Linden Lab offers a L$10,000 bounty for each previously unknown exploit that can be verified. Please report issues as soon as they are discovered!
Filing issues
There are two ways to file security reports:
* In the SEC project on jira.secondlife.com (PREFERRED). It's VERY IMPORTANT that you file issues in the SEC project, which is the only project set up so that only the reporter and Linden Lab can view the issue.
* Via email: security@lindenlab.com
For other issues:
* If you believe your account has been breached please attempt to change your password immediately and also contact support.
* If you are experiencing some other problem, please contact support.
* See Bug Tracker for information about filing non-security issues.
Category:Bounties Category:Bug Tracker
Security issues/ja

セカンドライフのセキュリティに関連する案件は以下に説明する手順でリンデンラボに報告してください。修正が提供される以前に、脆弱性の可能性がある事柄が広く世間に知れないようにすることでSecond Lifeを守りましょう。
では、どんな事例がセキュリティ案件と言えるでしょうか？ もし下記に示すように、セカンドライフそのもの・住人・住人の所有物などに危険性があるものであれば それは報告するべきエクスプロイトだといえるでしょう：
* 本人の同意なしにリアルライフの個人情報を公開する
* 所有物を破壊する
* 未許可でセカンドライフ/リンデンラボの資源へアクセスできるようにする
* クライアント、またはサーバーをリモートコントロールできるように侵害する
エクスプロイトを報告する際は可能な限り詳細を提供するようにしてください、使用している環境（Windows XP Service Pack2、Nvidia 6800 を使っているなど）、そして完全な再現方法もお願いします。未知のエクスプロイトが報告されたと確認された場合、リンデンラボは賞金として L$10,000を提供します。セキュリティに関する案件は発見しだいすぐに報告するようにしてください。
== 事象を報告する ==
セキュリティに関する事象を報告するには二つの方法があります。
* jira.secondlife.comのSECプロジェクトに報告する（もっとも望ましい手順です）。必ずSECプロジェクトに報告するようにしてください。 SECプロジェクトはその案件を報告した方とリンデンラボだけが内容を見ることができる特殊なプロジェクトです。
* security@lindenlab.comにメールする。
注意: SECプロジェクトとセキュリティ用メーリングリストは住民のかたの個人情報やSecond Lifeグリッドなどに関わるセキュリティ・エクスプロイトを報告するための専用窓口です。その他の事柄、アカウントの問題やアカウントのセキュリティに関する要望などはこちらでは処理されません。
その他に：
* もし自分のアカウントが侵入されたと思った場合は、まずパスワードを変えて、その後サポートへ連絡を取ってください。
* もしその他の問題がある場合もサポートへ連絡を取ってください。
* セキュリティ関連ではない一般的な不具合については問題解決のためのシステムを利用してください。
Category:Bounties/ja
Seduction Microcontinent

A037 or Seduction is a Microcontinent identified at Coordinates 760-762/928-934, Grid Sector G9, Western Ocean.
Seduction is formed of 14 sims and is a long and thin microcontinent. It is composed of a high number of islands. There is more dryland then flooded land. All sims look like a tropical beach paradise, with excesive vegetation. Land is divided into parcels both by water channels and by elevated land. There are low mountains between parcels and also between channels. Every sim has access to water.
In central sim Seduction Isle there is the highest Altitude, 98 meters.
Land is owned by a single estate and is available for sale. Also, there is Protected Land. Land With Restricted Access is present, but the entity orbs allow you to move in time.
== See Also ==
Second Life Geography
List Of Microcontinents And Sim Clusters
Oceans
SeedCapability

Client POSTs:
<llsd>
 <array>
 <string>MapLayer</string>
 <string>MapLayerGod</string>
 <string>NewAgentInventory</string>
 <string>EventQueueGet</string>
 </array>
</llsd>
Server responds:
<llsd>
 <map>
 <key>EventQueueGet</key><string>https://sim2.aditi.lindenlab.com:12043/cap/eb34cda6-0000-0000-0000-000000000000</string>
 <key>MapLayer</key><string>https://sim2.aditi.lindenlab.com:12043/cap/e05f9307-0000-0000-0000-000000000000</string>
 <key>MapLayerGod</key><string>https://sim2.aditi.lindenlab.com:12043/cap/899e2f11-0000-0000-0000-000000000000</string>
 <key>NewAgentInventory</key><string>https://sim2.aditi.lindenlab.com:12043/cap/469933ae-0000-0000-0000-000000000000</string>
 </map>
</llsd>
Seedable PRNG

See also: llFrand, llListRandomize, Pseudo-random_Number_Generator
Note: The 32bit_Hash example presents just the conversion to integer from llMD5String.
== md5 based seedable PRNG ==
It's not the fastest thing but it doesn't seem to have much if any output skew, and I couldn't detect any periodicity in the first 100,000 cycles.
//new md5 based seedable PRNG
//By: Gigs Taggart
//Released under BSD License.
//http://www.opensource.org/licenses/bsd-license.php
integer gSeed=0; 
string gLastHash;
prng_seed(integer seed)
{
 gSeed=seed;
}
integer prng_get()
{
 gLastHash=llMD5String(gLastHash, gSeed); 
 //the bitwise thingy gets rid of negative numbers
 return (integer)("0x" + llGetSubString(gLastHash, 0, 7)) & 0x7FFFFFFF;
}
default
{
 state_entry()
 {
 prng_seed(2007031901);
 string line;
 integer index;
 line = "";
 for (index = 0; index < 9; ++index)
 {
 line += " " + (string) prng_get();
 }
 llOwnerSay(line);
 line = "";
 for (index = 0; index < 30; ++index)
 {
 line += " " + (string) (1 + (prng_get() % 6));
 }
 llOwnerSay(line);
 llOwnerSay("OK");
 }
}
Category: LSL Examples Category: LSL Encryption
Select Land

=== Feature Design Document ===
(none)
=== Functional Spec ===
* Right clicking land > About Land will select the parcel and open a window showing information about the parcel
* Right clicking land > Edit Terrain will select the parcel and open the Edit Land tool.
* The land owners color overlay should appear when you enter Edit Land mode.
* Double clicking a parcel while you're in Edit Land mode will select the entire parcel.
* The land owners color overlay should disappear when you exit Edit Land mode.
* The yellow selection fence should disappear when you exit Edit Land mode.
=== Test scripts ===
Terraforming Test
Selection Test (Select Land section)
Selection test
=== Discussion for future improvements ===
(none)
=== Relationship to other features ===
 List of features that need to be tested when this feature changes, and why. 
(none)
=== User Guides ===
(none)
Select Objects

=== Feature Design Document ===
(none)
=== Functional Spec ===
(part of Build Tools Functional Spec)
Selections
* Must be in edit mode.
* Adding to selection - shift select
* Subtracting from a selection - shift select
* Drag-select
** You can start your drag select by clicking and dragging anywhere.
** You can limit the scope of your selection through options in the Tools menu
*** Select only my object
*** Select only objects I can edit
** You can change the drag select sensitivity
*** Select whole object (vs. only selecting a vertice)
*** Select whole object requires your drag select to competely enclose the object.
** You can change the look of the selection
*** Show hidden lines
* Select textures
** Select textures allows you to click individual sides of objects and texture them.
** Shift click sides to add or subtract them from the selection.
** If you already have an object selected when you change to "select texture", all sides of the object(s) will be automatically selected.
* Select linked part
** select linked parts allows you to select individual prims within a linked set
** Shift click other prims within the linked set to add or subtract them from the selection.
** If you already have an object selected when you change to "select linked parts", all prims of the linked set will be automatically selected.
Deselecting
* Hit escape
* Click another object
* Walk or fly (unwanted feature)
=== Test scripts ===
Object Selection Test
Selection Test
not to be confused w/
Selection test
=== Discussion for future improvements ===
(none)
=== Relationship to other features ===
 List of features that need to be tested when this feature changes, and why. 
Edit tools
=== User Guides ===
(none)
Selection test

NOTE: this test reflects only the changes to object and parcel management in Jan. 07. It needs to be integrated with the existing selection test plan, Selection_Test
==Overview==
Parcels and objects will no longer be deselected as soon as the first operation on them completes. The selections now stay around until 'all' operations complete.
In general, test overlapping parcel/object operations in the following way:
* start operation A
* start operation B
* end operation A
** parcel/object should still be selected
* end operation B
** parcel/object should be deselected
==Parcels==
Make sure that all parcel operations keep the parcel selected and can be completed (land purchased or sold, for example). Certain operations will silently fail if the parcel becomes deselected during the process, so it is important to carry the process through to selection.
Operations to test:
* Buy Parcel
* Sell Parcel
* Edit Land
* About Land
etc...
Ensure that as long as at least one operation is in progress, parcel remains selected. For example, right click on parcel and select edit terrain. Then right click on the parcel again and select about land. Close the edit terrain window. The parcel should remain selected. Close the About Land window. The parcel should become deselected. Right clicking on another parcel when either window is opened should select a new parcel and the windows should reflect the new parcel's information.
esp. check parcel media section and changing the media texture
==Objects==
Ensure that all operations that require an object selection can be completed.
Operations to test:
* Edit Object
** Object manipulation tools (translate, rotate, scale, etc)
* Sit on Object from a distance
* Attach / detach objects
* Open Object contents
* Buy Object
* Buy Object contents
* Inspect object
etc...
As before, make sure that overlapping object operations keep the object selected until every operation is completed. The object should be highlighted with an orange highlight as long as only a pie menu is open for that object. Any other window should display the object highlight in yellow and blue.
Self-Destruction

Change the number in llSetTimerEvent(30.0) to set the time, in seconds, that it will take for the object to disappear.
==Script==
// Davada Gallant (John Girard), WWIIOLers
// 30-second self destructor
default
{
 state_entry()
 {
 //upon creation, immediately start the timer
 llSetTimerEvent(30.0); // Change this to set time in seconds
 }
 //once the timer ticks off, kill the object
 timer()
 {
 llDie(); 
 }
}
Self Upgrading Script Enhanced

Thanks to Markov Brodsky's Self Upgrading Script and Jippen Faddoul's update to the idea, I was inspired to add to the flexibility and usefulness of their original works.
Markov Brodsky's original code is quite good, and I based my own implementation upon it, but it has an admitted flaw: It requires that all the scripts that use it have no spaces within the name. For me this will not do. I like my space ;D
Jippen Faddoul's update is also pretty good, but while it is nicely shortened and optimized, it can't handle being copied into the prim more than 2 times. This makes it unusable for my coding style. (Tweak, save, copy, test, repeat...)
So here's my edition to fix those shortcomings. (You may use this code freely and distribute it freely, but DO NOT even try to SELL it.)
// Self Upgrading Script by Cron Stardust based upon work by Markov Brodsky and Jippen Faddoul. 
// If this code is used, these header lines MUST be kept.
upgrade() {
 //Get the name of the script
 string self = llGetScriptName();
 
 string basename = self;
 
 // If there is a space in the name, find out if it's a copy number and correct the basename.
 if (llSubStringIndex(self, " ") >= 0) {
 // Get the section of the string that would match this RegEx: /[ ][0-9]+$/
 integer start = 2; // If there IS a version tail it will have a minimum of 2 characters.
 string tail = llGetSubString(self, llStringLength(self) - start, -1);
 while (llGetSubString(tail, 0, 0) != " ") {
 start++;
 tail = llGetSubString(self, llStringLength(self) - start, -1);
 }
 
 // If the tail is a positive, non-zero number then it's a version code to be removed from the basename.
 if ((integer)tail > 0) {
 basename = llGetSubString(self, 0, -llStringLength(tail) - 1);
 }
 }
 
 // Remove all other like named scripts.
 integer n = llGetInventoryNumber(INVENTORY_SCRIPT);
 while (n-- > 0) {
 string item = llGetInventoryName(INVENTORY_SCRIPT, n);
 
 // Remove scripts with same name (except myself, of course)
 if (item != self && 0 == llSubStringIndex(item, basename)) {
 llRemoveInventory(item);
 }
 }
}
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
// * The real start of the universe.
// * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
default {
 state_entry() {
 upgrade();
 }
}
As far as my testing was able to show, I was able to have spaces in my script names and I was even able to tack on a number at the end of my script for personal version tracking and had no troubles. I was able to copy the script into the same prim over and over again with only the latest ever staying.
Note: Due to the nature of SL, your script's name will alternate between "scriptname" and "scriptname 1", where "scriptname" is the actual name of your script.
Category:LSL Library
Seminole Island

Seminole Island is a Microcontinent located at Coordinates 1132-1139/994-996, Grid Sector A194, Eastern Ocean - Sharp Sea, near Sharp Continent. It also has the temporary name A194. This is one of the remnants of the teen grid estates.
It is made of 10 sims, each one whith the name Seminole Island. Unfortunately, all 10 are Land With Restricted Access, so no survey could be done and there is no data of what is on their surface.
== See Also ==
Second Life Geography
List Of Microcontinents And Sim Clusters
Oceans
SendPostcard

==Message Layout==
{
	SendPostcard 	Low		NotTrusted Unencoded
	{
		AgentData	Single
		{ AgentID		LLUUID		}
		{	SessionID	LLUUID		}
		{	AssetID		LLUUID		}
		{	PosGlobal	LLVector3d	}	
		{	To			Variable 1	} 
		{	From		Variable 1	} 
		{	Name		Variable 1	} 
		{	Subject		Variable 1	} 
		{	Msg			Variable 2	} 
		{	AllowPublish	BOOL		}	
		{	MaturePublish	BOOL		}	
	}
}
==Usage and Notes==
Category:Messages
SendPostcard CAP

POST:
<llsd><map><key>from</key><string>me@email.com</string><key>msg</key><string>Why hello there!</string><key>name</key><string>Test User</string><key>pos-global</key><array><real>263538.51737213135</real><real>251980.11839294434</real><real>342.60598754882812</real></array><key>subject</key><string>Postcard from Second Life.</string><key>to</key><string>you@email.com</string></map></llsd>
Response:
<llsd><map><key>state</key><string>upload</string><key>uploader</key><string>https://sim3507.agni.lindenlab.com:12043/cap/76db0b2c-c3c7-3be8-a8cc-77906ed7ab22</string></map></llsd>
SendUserReportWithScreenshot

Category:Capabilities
POST:
<llsd>
	<map>
		<key>abuse-region-id</key>
		<uuid />
		<key>abuse-region-name</key>
		<string />
		<key>abuser-id</key>
		<uuid>ffffffff-eeee-dddd-cccc-23e7775c9dce</uuid>
		<key>category</key>
		<string>45</string>
		<key>check-flags</key>
		<integer>0</integer>
		<key>details</key>
		<string>V1.21.5.98701
Abuser name: Test User
Abuser location: secondlife:///Crash%20Me/51/115/23
Enter my text here</string>
		<key>object-id</key>
		<uuid />
		<key>position</key>
		<array>
			<real>110.21762084960937</real>
			<real>78.232200622558594</real>
			<real>341.15731811523438</real>
		</array>
		<key>report-type</key>
		<integer>3</integer>
		<key>screenshot-id</key>
		<uuid>62329894-92db-5769-21a2-e1e7631e8dbd</uuid>
		<key>summary</key>
		<string> |Halfway| (secondlife:///Crash%20Me/51/115/23) [Disturbing the peace > Repetitive spam] {Test User} "Subject line here"</string>
		<key>version-string</key>
		<string>1.21.5 Win Intel Pentium Pro/2/3, Core GEFORCE 9600 GT/PCI/SSE2 </string>
	</map>
</llsd>
Response:
<llsd>
	<map>
		<key>state</key>
		<string>upload</string>
		<key>uploader</key>
		<string>https://sim2332.agni.lindenlab.com:12043/cap/64a50b41-d788-b14c-26cd-16f8bc50acc4</string>
	</map>
</llsd>