nyuuzyou/wikis huggingface dataset:
Brands

==External listings of Brands in SL==
Looking for a specific brand in Second Life? Try browsing these websites.
If you have your own business, it's a perfect idea to list it here. All directories mentioned below are free to join.
=== Categorized listings ===
* SL Business Directory & Second Life advertising - Second Life business directory, the one of the largest (more than 1200 companies). Free categorized listing of Second Life business. Allows to contact business owners. [Offline last checked on May 9, 2022]
* SecondPages - The YELLOW PAGES of SL with more than 800 entries - Search by categories or full text for real and virtual brands [Offline last checked on May 9, 2022]
* Second Life Yellow Pages, Jobs & Advertising - Yellow Lanes - Yellow Pages and job exchange for Second Life, free advertising since 2007. [Offline last checked on May 9, 2022]
* Second Life Locations Directory SL BEST PLACESecond Life Locations Directory Based on Real Time Traffic [Offline last checked on May 9, 2022]
=== Uncategorized (plain) lists ===
* New Business Horizons - List of companies and organizations in Second Life, most with SLURLs [Offline last checked on May 9, 2022]
* Tateru's Blog lists 139 businesses and non-profits - List created 2 July 2007 
Back to Marketing
Category:Marketing
Brautigan & Tuck Holdings

Brautigan & Tuck Holdings (ACE:BNT) is an estate company/conglomerate that is the virtual world operation of M2B LLC. BNT owns/manages 49 sims across SL with themes ranging from business, residential, to educational and military. Known collectively as "Ancapistan", the estates of BNT recognise the property rights of their residents, and provide top quality customer service, sim security, and infrastructure. BNT's company website is www.bntholdings.com which includes their land sales directory, listing many available properties of all kinds. Their sales and customer service personnel include: Duchess Shepherd, Kaddan Yue, Heather McKay, Cliff Eclipse, Hamncheese Omlet, Dylan Talon, and Rico Warilla..
BNT is an Extended Support Customer of Linden Lab, is a Registered Solutions Provider, Registration API participant, and is one of the Community Registration Beta project participants.
===History===
Founded in October of 2006, BNT is one of the older estate companies in Second Life. It was founded by CEO IntLibber Brautigan and his first partner, Tavi Tuck subletting land in the Surreal Estates. 
A main target of the 2007 wave of PN griefing, BNT first assumed a 'War on e-Terror' posture to the security situation, developing the best security service in SL, Ng Security, and some innovative security devices like the Rat Thing agent profiler. Ng also infiltrated griefing groups to study them and engage in psyops. With greater understanding of the causes and participants in griefing, Ng changed its focus to adopt a 'juvinile crime' model of dealing with griefing, with economic opportunities and paths to legitimization for griefers who wanted a clean slate and a fresh start. With the cooperation of Linden Lab's Michael Linden, BNT's Ng team made significant strides in 'defanging' griefing groups by unbanning creative, productive members and giving them creative outlets and economic opportunities.
BNT was also the largest business ever to 'go public' on an inworld stock exchange, going public on the World Stock Exchange in April of 2007, raising L$13.5 million, which funded BNT's expansion from then 12 sims to 34 sims. Since that time, BNT has further expanded to 50 sims.
With over 50 sims, it is one of 35 estates receiving Extended Support from Linden Lab. With a professional, mature and experienced staff, BNT is able to provide 24/7 customer service in several languages.
BNT provides services to virtual and RL corporate clients, like Woodbury University, MBC, SL-Newspaper, Space Daily, and many others. In October of 2007 BNT founded the Ancapistan Capital Exchange to servie its Ancapistan continent and the SL community.
Brazilian Viewer Localization Project

__NOTOC__
==CURRENT STATUS:==
:* 2009-June-30: We have finished all submissions for Viewer 1.23. The next time we make changes/updates for translations in the viewer will be August 2009.
:* BUT, we are still keeping track of any bad translations or language bugs that you find!
:** Please report any translation bugs of the viewer in this document.
:** For more information , please contact: Ramzi Linden
		 	
{| border="0" cellspacing="0" cellpadding="0" width="100%"	
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"	This Project	This Project
		 	
{| border="0" cellspacing="0" cellpadding="0" width="100%"	
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"	Tips	Tips
		 	
{| border="0" cellspacing="0" cellpadding="0" width="100%"	
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"	What To Do	What To Do
		 	
{| border="0" cellspacing="0" cellpadding="0" width="100%"	
{| style="width="30%"; font-size:95%; text-align:left; padding:-2px; background:none" cellpadding="0" cellspacing="0"	Questions	Questions
Category:Localization
Breedable Microcontinent

This is a Microcontinent, placed at Coordinates 768-770/1372-1373, in Grid Sector G13, Northern Ocean. Also, it has the temporary name A128.
It is composed of 6 sims, forming a rectangle. There is a lake in the center, with an island of high mountains (about 60 meters). All the remaining land is smooth, flat and divided by fences. Overall, this place looks like a big rench. This is a paradise for those who love virtual animals, mainly horses.
No Land With Restricted Access exists here and Protected Land is also present. There is land for sale.
This is not the only place for breedables. Many other places exist.
== See Also ==
Second Life Geography
List Of Microcontinents And Sim Clusters
Oceans
Bringing my Business into SL

Thank you for your interest in Second Life and the Second Life Grid. Here's ten steps that will help you bring your business into Second Life.
Landing in Second Life, a virtual world, has been compared to arriving in a new city. It takes awhile to get the lay of the land, to meet people, to find places you want to go and things to do. It takes even longer to learn "the ropes" - the social behaviors and customs that set new-comers apart from long-time residents. With this in mind, here are ten suggestions to help you get started on Second Life Grid:
*Register, create, and name your avatar. It will take some time to learn how to move and interact.
*Go hang out at The Shelter (or one of the Resident-run spaces for new members); make some friends, learn how to dance, and get help from the friendly staff and visitors.
*Find and attend classes and events - you'll find them in the Event Listing on secondlife.com or inworld.
*Subscribe and read Second Life Periodicals, Business Blogs, mailing lists, and other public information about Second Life.
*Try your hand at building in one of the public sandboxes.
*Buy some land and settle down - buy or build a house and furnish it.
*Join a group, go to meetings or events with members of the group.
*Talk to Residents about what they're doing in Second Life and what they like - and dislike - about it.
*Think about your audience in Second Life and how to engage them.
This will help get you started. We recommend spending 10-20 hours in Second Life. Once you have the lay of the land, start thinking about your business and/or education objectives, learn from others how to create a sustained experience that engages your customers or students and meets your objectives. For assistance, look at How Organizations Use the Second Life Grid, Resources, and Solution Providers.
Bug Tracker/Conduct

#Redirect Linden_Lab_Official:Community_Participation_Guidelines
In short: be excellent to each other, help us make Second Life better, and don't be a jerk.
But if you need specifics, here's examples of behavior which subject you and your content to being removed from the Issue Tracker:
* Using the Issue Tracker to promote a business, cause, blog, website or anything not relevant to the issue at hand.
* Using the Issue Tracker as a forum. It is a technical reporting tool. Comments & Issues which are not bug reports or new feature suggestions will be removed/closed. If you would like to comment on a recent announcement by Linden Lab or make a proposal and discuss it with other Residents please start a discussion in the Second Life Forums. 
* Personal Attacks - Do I need to repeat myself? If your comment isn't useful, don't post it.
* Flaming, Trolling - Flaming (posting a comment that is intended to incite anger or directly attack a person or persons) and trolling (a post with an intentionally contrary opinion written with the intent of inciting or getting argumentative opinions) are NOT appropriate. Again, keep to the facts of the issue at hand. Posts that disregard this are subject to deletion, posts that try to sneak around it even moreso.
* Private Discussions - The Issue Tracker is about finding solutions to bugs and problems, NOT posting your personal opinions or off-topic rants. We love productive feedback, so stick to the technical details of the matter at hand.
* Editing Wars - Repeated changes to a resolution, priority or classification of an issue. This wastes everyone's time.
Category:Bug Tracker
Bug Tracker/Details

To report a new bug, do the following:
# Click the "Create New Issue" link in the blue navigation bar towards the top of the screen. (If you don't see this, make sure you are logged in to JIRA.)
# On the first page:
#* Select a Project that most closely matches the kind of bug you are submitting - see Projects and Components.
#* Select "Bug" as your Issue type.
#* Click "Next".
# On the second page:
## Enter a concise but informative summary (title) for the issue
## Select the priority (severity) of the bug. For example, a "Showstopper" bug might render the program useless, but a "small" bug might be merely cosmetic. Click the Help icon next to the dropdown for more details.
## Select components that narrow the scope of the bug. You can select multiple components by Ctrl-clicking.
## Choose the versions that the bug effects. You should only select those versions where you have observed the bug, and only select a "First Look" version if the bug only applies to First Look.
## Describe the computer environment in which the problem occured. For example, if you have noticed that the bug only occurs with certain hardware or software configurations.
##* The best way to report this information is to paste the info that comes from inside Second Life viewer. (Help menu > About Second Life...) Certain facts might be relevant (Windows vs Mac vs Linux machine, or graphics card model, or headset models for voice features). If configuration truly doesn't matter, you can leave it blank.
##* For example, "Only happens with Mac OS X 10.4.1," or "Seen only with NVIDIA GeForce Go 7800 card," etc.
## Enter a detailed description of the issue, and be sure to include:
##* Steps (1,2,3...) to reliably reproduce the bug-- How to make the bug happen. If you cannot identify the specific steps, describe what seems to lead to the bug. Try to make this as simple as possible while still being specific enough to reproduce the bug. Simpler reproductions make it easier to narrow down the causes.
##* OBSERVED results (what happens when the bug occurs)
##* EXPECTED results (what behavior you would have expected instead)
##* As a reminder: be as detailed as possible without including personal information!
## If you have a screenshot or video of the bug, or any other relevant file, you can attach it under attachment. Note that it has a 10MB size limit per file. You can also attach additional files later. (See Debug Help for various ways to hunt for such additional information.)
## If you are a programmer and are attaching a patch for the source code, enter the source version the patch is against and check the patch attached box.
# Finally, click "Create" to create the new issue.
Bug Tracker/Help LL

Here's how you can help Linden Lab track and fix bugs.
== Submit patches ==
Do you have coding skills? Visit our Open Source Portal to learn more!
== Learn about the Quality Assurance process ==
== Vote for issues ==
You can vote for new features and bugs that you wish to see fixed by Linden Lab, and view all issues by # of votes. The Issue Tracker uses approval voting, so you can vote for as many (or few) issues as you'd like, and you get 1 vote per issue.
Votes are readily used as part of our prioritization process. Keep in mind that since we need to look at aspects such as feasibility and the time required for development, a highly-voted issue isn't necessarily going to be resolved ahead of a lesser-voted, but more doable one.
== Marking Duplicates ==
If you notice an newer issue that's a duplicate of an existing issue with a lot more comments, patches, or votes, feel free to choose Resolve with a status of Duplicate. But when you do this, please also choose Link, then specify the main bug #. This reduces confusion and ensures that bugs that are often reported get the most attention. It also allows the duplicates to be reviewed from one central location, to show they're truly duplicates.
== Resolving support issues ==
If you're not sure, learn from and leave this to technically experienced Residents who can spot the difference between a support issue and a bug — it's not always a simple matter to figure out. You should at most Resolve a report that seems to be a support issue. Resolving an issue puts the responsibility back on the reporter to substantiate otherwise.
== Resolving bugs that you can't reproduce ==
This is also best left to the technically adept. If you follow the same steps in an issue with the same environment, yet can't reproduce the bug, you should resolve the bug. Be careful: for example, if a bug is related to graphics rendering and you don't have the same graphics card, that's not the same environment and you can't make this determination.
== Reproducing bugs ==
This one is very important! If you can create a step-by-step list to reproduce the bug in the bug report, this helps Linden Lab concentrate on bugs that can be verifiably fixed. Unless a bug can be reproduced, it's impossible to know if it has been fixed or not. Do what the bug reporter said they were doing, write a better step-by-step list of things you did to cause the bug to happen, and add it to the bug — make it clear that you've successfully reproduced the bug. Such bugs with solid reproductions get higher priority in the development process, and help bug triages to work more efficiently.
=== Sorting issues in the wrong categories ===
If an issue is in the wrong category (e.g., a VWR issue that belongs in SVC), it should never be resolved as Misfiled. Instead, leave a comment here listing the issue and where it should belong. A volunteer will move it to the appropriate place.
Bug Tracker/Searching

Do you want to find something specific in the Issue Tracker, or or scan to see if your bug's been reported by someone else?
Issue Tracker searching can be frustrating, but it gets easier if you know how to use search parameters. 
=== Official Atlassian Instructions ===
* Atlassian's JIRA documentation on "Searching for Issues"
=== Quick JIRA Search How To ===
* think some words (at least 2; 3 or 4 can work better) which reasonably can be present in the hypothetical title of the JIRA you're looking for;
* write those words in the "Quick Search" form, which is in the upper-right corner of any JIRA page, adding a '+' before each word
* getting too many results? on the results page, look on the left side for the "Query" form. "Comments" and "Description" checkboxes are enabled by default. Disable "Comments" checkbox and try again. If you still get too many results, disable "Description" checkbox too.
* if you don't get any results, or results don't match what you're looking for, change your keywords and retry
=== Screencast ===
Category:Bug Tracker
Bug Tracker/Searching/pt

__NOTOC__
= Pesquisando no Bug Tracker =
Você quer encontrar algo específico no Issue Tracker, ou sondar para ver se o seu bug foi relatado por outra pessoa? 
Pesquisar no Issue Tracker pode ser frustrante, mas fica mais fácil se você souber como usar os parâmetros de busca.
=== Instruções Oficiais da Equipe Atlassian ===
* Da equipe Atlassian de desenvolvimento do JIRA, documentação sobre "Searching for Issues" (Procurando por problemas)
=== Como efetuar uma rápida pesquisa no JIRA ===
* Achar algumas palavras (pelo menos 2, 3 ou 4 pode funcionar melhor), o que razoavelmente pode estar presente no hipotético título do JIRA que você está procurando;
* Escrever essas palavras no formulário "Quick Search", que está no canto superior direito de qualquer página do JIRA, adicionando um sinal de '+' antes de cada palavra
* Obteve muitos resultados? na página de resultados, procure no lado esquerdo, o formulário "Query" (Consulta). As caixas de seleção de "Comments" e "Description" devem estar ativadas por padrão. Desabilite a caixa de seleção de "Coments" e tente novamente. Se você ainda receber muitos resultados, desabilite também a caixa de seleção de "Description".
* Se você não obteve qualquer resultado, ou resultados obtidos não corresponderem ao que você está procurando, altere as palavras-chave e tente novamente. 
=== Tela de exemplo ===
Category:Bug Tracker
Bug Tracker/Status

Here's how Linden Lab uses the workflow status and resolution field:
; Awaiting Review : Initial state when an issue/ticket is created or when it is reopened closed state. All issues in in this state will be reviewed and triaged.
; Been Triaged : This state indicates that the issue is being reviewed by Linden Lab.
; Accepted : When an issue has been imported to an internal Linden Lab project, it will be marked as Accepted.
; Needs More Info : The issue lacks actionable information. Add the info or it CAN'T be investigated.
; Information Provided : The issue has been updated with the necessary information.
; Closed :
:; Resolution = Contact Support : The issue does NOT belong in the Bug Tracker, and needs to be handled through the Support Portal or Second Life Answers.
:; Resolution = Expected Behavior : This is NOT a bug and functions by design See Expected Behavior aka Not a Bug.
:; Resolution = Duplicate : There's another issue about the same problem.
:; Resolution = Unactionable : Problem described in the ticket is not in a form that action can be taken (i.e. it's too broad)
:; Resolution = Not Applicable : The Reporter has decided to close the issue.
== Diagram of Workflow ==
Note:
* Diagram does not have all the transition arrows.
Bug Tracker/ja

Second Life で思うように動かない機能はありますか？バグを発見したのかもしれませんよ！
== Bug (バグ) って何？ ==
複数の人が同じ状況の中で起こる意図しないコンピュータ障害のことです。
バグ でない ものは？
* アカウントに固有だったり、サポートに対する問題では「ありません」。 - 課金トラブルなどの、返事が必要な個々の事象は「違います」。それは、サポートポータルに行ってください。
== Bug Report (バグ報告) って何？ ==
バグの説明書きで、あなたと私たちの間で共有するものです。役に立つバグ報告はこのようなものです。
* 理解しやすい - ドライブの道案内をするときは、目立つものを強調して説明しませんか？バグ報告はこのような感じであるべきです: 分かりやすい手順があって、お友達があなたの手順に沿ってできるものです。
* 再現できる - 残念なことに、Bigfoot のように、証拠を見つけるのが難しいバグがあります。しかし多くのバグは順番に手順を踏めば確実に発生します。バグを確認して、私たちが藪の中から捕まえられるようにしてください。
== 良いレポートの作り方 ==
これらを念頭に置いて、
# Bug Tracker へ行き 手順を読んでください。
# Bug Tracker を検索し、バグが既に報告されていないか確認してください。他の人が同じ問題に直面していることを知ると、気分が安らぎます。
# 一致するものがなければ、バグ報告を書きます。次のことを含めて書いてください。
## 再現手順
##:可能な限り詳細に、ユーザがこういう一連のアクションをとると問題が発生するということを説明してください。特定の条件がある場合、例えば特定の区画だとか、グループ権限にこのような権限がついているとかを、丁寧に説明してください。レポートを提出する前に、他の人を捕まえて説明通りにやって同じ問題が起きるかを試してみてください。説明はシンプルにするのは良いのですが、シンプルでなくても完全であればもっと良いです。
## 期待する動作の説明
##: 「オブジェクトが赤にならないといけない」とか「アバターはシャツを着ていなければならない」とか。
## 実際の動作の説明
##: 文章に画像、ビデオ、イラストが添えられていると、もっと良いです。
## 補足資料の添付
##: トラブルが、ビューアのクラッシュやサーバとの接続不良(例えば、もらえるものがもらえなかったり、インワールドで不測の事態が発生したりする場合)であれば、ビューアのログファイルを添付してください。問題が発生した時刻を可能な限り正確に特定して、私たちがログの中で関連する情報を見つけられるようにしてください。Finding Log Files に、ログファイルの探し方があります。
ゴールは 開発者が同じものを見て、バグを追跡し、修正できるように、自分が見たものを開発者に説明する ことです。
== 私はギークじゃないから助けが必要なんだよ！ ==
心配しないでください、みんな最初は新人でした。Bug Tracker の多くのディスカッションにはエキスパートな住人がいて、新しいバグ報告者を助けてくれます。
== Second Life が たった今 広範囲のサービス障害を起こしている場合は？ ==
一般的に、ログイン障害、テレポート障害、Grid Status Reports に出るようなもので既に私たちが対処しているものについて、バグ報告を提出する必要はありません。
== 見つけたバグが とっても 深刻で共有されるべきものでない場合は？ ==
リアルの個人情報が脅かされるような情報漏洩、コンテンツの破壊、その他可及的速やかな修正を検討する必要のある深刻な事態に対する私たちのセキュリティ障害に対する対応手順を知ってください。 
== バグを報告したんだけどまだ直ってないよ！なんで？ ==
私たちはたくさんのバグを修正していますが、全ての バグを修正できるものだと考えるのは現実的でありません。詳しく見てみましょう:
* 私たちが何を知ってるというの？ 再現できなかったり情報が足りなかったりするバグに対してアクションを起こすことはできません。証拠のない犯罪を警察に通報するようなものです。 (バグは犯罪ではないですが、確実に私たちは悩まされます！)
* これは優先度が高いの？ 例えば、多くの住人に影響する持ち物紛失バグは、数人だけしか気づかない見た目の異常よりは優先度ははるかに高いです。
* 依存関係は？ Second Life は複雑なシステムで、一見 そのバグが直すのが簡単に思えるものでも、私たちは関連する部分にさらに障害を作りこまないように直す必要があります。
== どのバグが直ったのかってどうやったらわかるの？ ==
Bug Tracker を検索するか、もしくはそれが難しいと思ったら、リリースノートを確認してください。バージョンごとに変更内容の詳細なハイライト記事が載っています。
== Bug Tracker での嫌がらせを報告するには？ ==
不毛な議論はやる気を失せさせ、ルーズで、時間の無駄です。時間は障害を修正するのに使った方がよっぽどよいです。ガイドラインに違反するような煽り行為には耐えられません — 
Bug Tracker を居心地の良い空間にするために、嫌がらせ行為の報告をお願いします。あなたのご協力をよろしくお願いします！
# Second Life ビューアで (Web ではありません)、メニューから ヘルプ > 嫌がらせを報告する を選択してください。
# 全ての欄を埋めてください。全ての嫌がらせカテゴリが Bug Tracker に対応するわけではありませんが、例えば、不寛容などがあるでしょう。
# 詳細 欄に、不快に感じるコメントへの直リンを貼ってください。コメント欄かコメントがある記事にマウスを当てると出てくるリンクアイコンをクリックすると、取得できます。
#: 
# 嫌がらせの報告 をクリックすると、Bug Tracker の管理者がじきに調査します。
嫌がらせの度合いにより、違反者は警告を受けたり、Bag Tracker や、Second Life 自体から永久に BAN されたりします。
== もっと知りたい？ ==
バグ報告の基本を学んだら、一定の時間をかけて理解してください。そして、
* How to report a bug - 質問が上で答えられていなければ、こちらを見てください。以下のハイライト記事があります。
** 探し方
** Community Participation Guidelines
** 対応状況一覧
* Bug Tracker カテゴリ - Bug Tracker に関する全ての記事が載っています。
Category:Bug Tracker
Bug Triage/YYYY-MM-DD

2010/09/07
Meu nome de usuária no Second Life é LadieDarkie Glassfield e preciso agendar uma triagem o mais urgente possivel ,estou recorrendo à essa pagina porque não encontrei um portal de ajuda.Meu avatar funcionava corretamente ate o dia 2010/09/05quando entrei ontem dia 2010/09/06 o meu avatar nao carregava o inventario e quando conseguiu carregar nao entrava em modo aparência ,não estou conseguindo
vestir nem skin nem shape no meu avatar e já tentei todas as possibilidades inclusive as oferecidas na opção Advanced tentei tambem land de debug e objetos para debug
meu avatar nao tem mais nada anexado a ele roupas ao objeto nenhum
e nao consigo vestir skin shape nem entrar em aparencia preciso de ajuda urgente
Tenho casa e muito dinheiro investido dentro do jogo 
Por Favor peço a ajuda de vocês urgentemente
Obrigada
LadieDarkie Glassfield 
My user name in Second Life is LadieDarkie Glassfield need to schedule a screening and the most urgent possible, I'm resorting to this page because it could not find a help portal .My avatar worked correctly until the day 2010/09/05 when I entered yesterday 2010 / 09/06 my avatar does not carry the inventory and when he did not charge went into appearance mode, I'm not getting 
dress or skin or shape in my avatar and I tried all possibilities including those offered in the Advanced option also tried to land and debugging objects
my avatar does not have anything else attached to it any clothes to the object 
wear skin and I can not get in shape or appearance need urgent help 
I got home there and a lot of money invested in the game 
Please I beg your help urgently 
Thanks 
LadieDarkie Glassfield
Moira Draconia 
My username is Moira Draconia. My avatar has worked correctly until 2011/02/18 when I have not been allowed to login. It would give me a time a few minutes away to come back, but then when I tried to log in again it would give me another time. It didn't matter if I waited a few minutes or an hour, it kept perpetually not letting me log in. 
I used an alt to log in and noticed it appears that Moira Draconia is online always, even though the avatar should not be logged in. I discussed it with some sl users and it was suggested it might be "ghosting". I am not sure how to fix this problem any advice would be appreciated. I am still unable to login. 
Moria Draconia