text:
Wikipedia:Username policy

This policy describes what kinds of usernames are acceptable on the English Wikipedia and how unacceptable or doubtful usernames can be dealt with. It also specifies that a user account should be used only by one person, and that in most cases one person should use only one account.

You choose your username when creating a user account. All contributions made using that account will then be attributed to the chosen username (contributions made while not logged in to any account are attributed to the user's IP address). It is also possible to request a change of username, and have your past contributions re-attributed to the new name.

This policy applies to usernames on English Wikipedia. However, in most cases you will be able to use the same username and password to log in to other language Wikipedias and other Wikimedia Foundation supported projects. See Unified login.

Guidance for new users
Your username is a nickname that will identify your account and thereby all of your contributions to Wikipedia. It can be your real name if you so choose, but you should be aware of the risks involved in editing under your real name before choosing to use or disclose your real name on Wikipedia. Wikipedia usernames are case sensitive, but the first letter is always automatically capitalized. By default, your username appears in your signature on posts to discussion pages. For further details on signatures and how to customize them, see Signatures.

You must keep in mind that, once chosen, a username cannot be easily changed, and changing your username doesn't hide your previous username from all of the edits that you've made while using it (such as the signature of your previous username that you left on any talk pages, messages, discussions, and replies). For example, if "Dr. Franz Schröder" is your real name, and you choose this to be your username, your real name and doctorate will be evident on your edits, on history pages, and (unless you change your signature) on all posts, messages, and replies that you make to talk pages and discussions. It is highly recommended that you read and understand the section on using your real name as your username before you decide to do so. Likewise, reusing a name here which you also use on other sites may be as revealing as using your actual name.

You will be required to specify the username that you'd like to use when you are creating a new account, and you will subsequently use it (together with your password) to log in to that account. Once you have an account, you may create a user page, titled "User:XXXX" (where "XXXX" is your username), to provide relevant information about yourself to other Wikipedians. You or any other editor may also create a user talk page, titled "User talk:XXXX", that people can use to contact you.

The MediaWiki software will not allow you to register a new account with a username that is already taken by another account, nor will it allow you to register a username that is too similar to another account. You can check whether or not a username is already taken; if the username is not listed when you enter it into the username search, it means that the provided username is not taken. Please note that the page does not return usernames that are too similar; it only returns a match if the exact username you enter is already taken. You may still be able to obtain a username that is too similar to another account under certain circumstances; see below.

Your username can be virtually any string of characters (subject to a few technical limitations). However, it should be a name which other users will be comfortable with and which does not interfere with the project. A controversial name may give a bad impression to other users, and avoiding this is in your own interest. This page describes certain types of usernames that are specifically disallowed, primarily because they can be considered offensive, misleading, or promotional, or imply that the account does not belong to an individual.

Inappropriate usernames
This section lists the types of usernames that are considered inappropriate. The same criteria also apply to signatures.

These lists are not necessarily exhaustive. Use common sense in applying these rules; a username containing a word that may seem offensive in one context may have a very different, more benign meaning in another. For guidance on how to deal with inappropriate usernames if encountered, see below.

Disruptive or offensive usernames
The following types of usernames are not permitted, and will be immediately blocked upon discovery, because they are disruptive or offensive:
 * Usernames that are likely to offend other contributors or cause disruption to productive Wikipedia processes or discussions, or make harmonious editing difficult or impossible to achieve; e.g. by containing profanities, or referencing highly contentious events or controversies.
 * Usernames that are blatantly profane, violent, threatening, or sexually explicit, or that advocate or encourage any such behavior (including acts that are deemed by most societies as either extremely immoral, criminal, or illegal).
 * Usernames that deliberately offend, dehumanize, attack, demean, disparage, discriminate, or support or advocate any such behavior toward any race, religion, gender, sexual identity, sexual preference, political affiliation, or social group or status, or imply the intent to do so. Examples include:
 * Usernames that contain discriminatory attacks, racial slurs, or pejorative terms
 * Usernames that praise highly contentious people, groups (also known as "hate groups"), or events—future, past, or present—that currently allocate, have allocated, or plan to allocate efforts or resources toward afflicting direct discriminatory, social, physical, or emotional harm toward those who identify as part of any of these groups.
 * Usernames that contain or imply personal attacks, or imply the intent to personally attack, harass, or threaten other Wikipedia editors.
 * Usernames that appear intended to disrupt legitimate Wikipedia discussions and processes by provoking negative emotional reactions from other editors (also known as "trolling").
 * Usernames that show or imply the intent to vandalize, disrupt, or engage in bad-faith edits or behaviors that are clearly not intended to help build, expand, or grow the encyclopedia in a positive or collaborative manner.

These accounts, upon their discovery, should be immediately blocked by administrators, and consideration should be given, with appropriate judgment, if the username should be redacted from any logs or edit revisions - especially if they're grossly offensive or destructive in nature, and likely to offend many editors. Note that usernames that are inappropriate in another language, or that represent an inappropriate name with misspellings and substitutions, or do so indirectly or by implication, are still considered inappropriate.

Usernames with libelous, contentious, or non-public information
The following types of usernames are not permitted, and will be immediately blocked upon discovery, because they violate highly important and serious Wikipedia policies:

 * Usernames that contain contentious or disparaging statements about another person (whether they be another editor, a notable living or recently deceased person, etc).
 * Usernames that are clearly libelous, contain blatantly false or disparaging statements or accusations about another person, or constitute blatant violations of Wikipedia's policy on the biographies of living people.
 * Usernames that contain any non-public, private, or personally identifiable information about another person, or contain any other information that would be deemed appropriate for suppression by an Oversighter; e.g. usernames that state what the password to the account (apparently) is.

These accounts, upon their discovery, should be immediately blocked by administrators. If such usernames are libelous or contain information that is usually suppressed (such as disclosure of non-public personal identifiable information about another editor, or blatantly libelous statements made about a notable living person), the username should be suppressed from all logs by an Oversighter to protect Wikipedia and the subjects involved from any kind of negative fallout or harm as a result of the account or username creation. Requests for removing attack usernames from logs should be reported to the global Stewards team for evaluation and private removal from all WMF projects. This can be done either via IRC in the channel or via email to the stewards VRT queue at.

Misleading usernames
The following types of usernames are not permitted because they may be misleading in a way that disrupts the project:
 * Usernames that impersonate other people (see and  below).
 * Usernames that give the impression that the account has permissions that it does not have; e.g. by containing the terms "administrator", "bureaucrat", "steward", "checkuser", "oversight", or similar terms, such as "admin", "sysop", or "moderator".
 * Usernames that imply that the account has explicit ownership of certain articles, content, or topic areas, or that they have any kind of "power", "command", "control", or "authority" over other editors, or that a different level of accountability and application of Wikipedia's policies and guidelines should be enforced (such as implying that certain policies do not apply to them).
 * Usernames that could be easily misunderstood to refer to a "bot" (which is used to identify bot accounts) or a "script" (which alludes to automated editing processes), unless the account is of that type.
 * Usernames that give the incorrect impression that the account is officially affiliated with the Wikimedia Foundation; e.g. by containing "WMF".
 * Usernames that resemble IP addresses (as these are expected to designate non-logged-in users), timestamps, or other names which would be confusing within the Wikipedia signature format.
 * Usernames that appear similar to naming conventions used by community administrative processes, such as those starting with Vanished user (see Courtesy vanishing).

For accounts with usernames that are in this category, you should assume good faith in cases where the username could be interpreted ambiguously. For example, a new user whose career is as a sysop might include that in their username, unaware of the policy prohibiting it. An attempt to discuss the username policy and concern with the user, and a request that they change their username should typically be attempted before considering further action. In cases where the violation of policy or the user's intent is clear, or likely created in bad faith, you should exhibit the use of common sense and fair and level-headed judgment when determining the appropriate action to take. These clear violations should be reported by following the instructions on Usernames for administrator attention.

Promotional usernames
The following types of usernames are not permitted because they are considered promotional:
 * Usernames that unambiguously represent the name of a company, organization, website, product, musical group or band, team, club, creative group, or organized event (e.g. TownvilleWidgets, MyWidgetsUSA.com, TrammelMuseumofArt, OctoberfestBandConcert2019). However, usernames that contain such names are sometimes permissible; see below. (Usernames which represent the subject of a biographical article are not considered promotional; see )
 * Email addresses and URLs to domains or websites (especially if they promote a commercial web page) and don't simply identify a person. Although usernames that only contain plain domain names on their own (those that do not include the top-level domain, such as,  ,  , etc. at the end) are sometimes acceptable (such as when the purpose is simply to identify the user as a person), they are inappropriate if their primary purpose is to advertise, promote, sell, gain support, or increase the attention or user-base audience of any person, company, market, product, channel, website, or other good or service. This includes any kind of websites that function in order to generate any kind of income or revenue for the owner. Examples include Patreon links or links to pages asking for donations, or revenue-generating click-thru links to vendors. All pages that are built or designed in one or more of these manners should be considered a commercial web page, and hence considered inappropriate for a username.

A user who both adopts a promotional username and who engages in inappropriate advertising or promotional edits or behaviors – especially when made to their own user space or to articles about the company, group, or product – can be blocked from editing Wikipedia, and are often blocked much sooner than users who engage in only one of the two behaviors. In such cases, administrators should examine the user's edits to decide whether or not to allow them to create a new username. If there is evidence that the user would continue to edit inappropriately under a new username, the blocking administrator should enable the "autoblock" and "prevent account creation" block settings. Otherwise, the user should be offered the opportunity to create a new account or have their current username changed. Before taking action, any disagreements as to whether a particular username is acceptable or not should be discussed at Requests for comment/User names first.

Usernames implying shared use
Because Wikipedia's policy states that user accounts cannot be shared between more than one individual, the following types of usernames are not permitted because they imply shared use:
 * Usernames that are simply names of companies or groups are not permitted (these also fall under above).
 * Personal usernames that imply shared access, such as "Jack and Jill", are not permitted.
 * Usernames that are solely the names of posts, positions, roles, or job titles within organizations, such as "Secretary of the XYZ Foundation", are not permitted, as such posts or positions may be transferred or held by different persons at different times.
 * However, usernames are acceptable if they contain a company or group name but are clearly intended to denote an individual person, such as "Mark at WidgetFactory", "Jack Smith at the XYZ Foundation", "FacebookFanatic87", etc.

Remember that promotional editing is not permitted, regardless of any account's chosen username. The conflict of interest guideline advises all users to exercise caution if editing articles about businesses, organizations, products, or other subjects that they are closely connected to. If you choose to edit articles that are in any way related to your company or group, you will need to carefully follow Wikipedia's advice on editing with a conflict of interest.

Non-script usernames
The following types of usernames are not permitted due to the difficulty with some web browsers in viewing non-language Unicode characters:
 * Usernames that contain emoji.
 * Usernames that are considered to be emoticons or otherwise "decorative".
 * Usernames that use any non-language symbols. This includes:
 * Symbols and characters unrelated to the list of writing systems.
 * Symbols and characters that are on the block lists at Unicode symbols.

Note that this restriction does not apply to signatures, which are governed by Wikipedia's policies on the use of signatures.

Confusing usernames
Some usernames appear problematic without fitting clearly into any of the above categories. This is often the case with confusing or extremely lengthy usernames, which are highly discouraged but which are not so inappropriate on their own as to require action.

Confusing usernames can often be a red flag for other problems. An editor with a confusing username or signature may be blocked sooner than usual for other inappropriate behavior, such as disruption or vandalism, if their confusing username contributes to the disruption.

Exceptions
Some usernames that appear to be in breach of this policy have been allowed to stand by consensus because they were created before a change in the policy that would now prohibit such names (see grandfather clause). If you find an apparently problematic username being used by a long-standing editor, it is likely that the matter has been discussed before. Please search that user's talk page (and archives if applicable), and the archives of the administrators' noticeboards and requests for comment on usernames, before deciding to take action as described below.

Dealing with inappropriate usernames
If you encounter an inappropriate username as described above, there are various actions you might take. Use common sense in making your choice, and avoid "biting" newcomers.

No action necessary
If the name is not unambiguously problematic, it may be sensible to ignore it. Assume good faith, and also note the exceptions in the section on inappropriate usernames. Also, except in extreme cases, it is probably not worth taking action unless the user has made at least one recent edit.

Talk to the user
If you see a username that is problematic but was not obviously created in bad faith, politely draw the user's attention to this policy, and try to encourage them to create a new account with a different username. If you want, you can use the {{subst:uw-username}}, {{subst:uw-uall}} or {{subst:uw-coi-username}} template for this.

Request for comment
If, following an attempt to discuss a problematic username with the user, there is still doubt or disagreement as to whether the name is appropriate, you may open a Request for comment on the username, inviting other users to discuss the issue.

Report blatant violations
If you believe that a username needs to be immediately blocked and is an obvious violation of policy, you can report it to Usernames for administrator attention. This page should only be used for clear and egregious username violations that merit an immediate block and without any discussion or warning beforehand.

Do not both warn a user account or discuss the username and your concerns with a user account, and file a report against the user account at Usernames for administrator attention at the same time. A warning or discussion by another editor should be perceived as an invitation or an encouragement for the user to change their username or otherwise resolve the matter at-hand, while filing a report against the account invites a block to be immediately placed and without warning or discussion beforehand. These two actions directly counteract with one another; performing both actions can cause confusion, frustration, and the biting of newcomers where the assumption of good faith likely should have been the preferred initial response.

Report other problems
If the user with a bad username is breaching other policies, such as those against spam or vandalism, follow up using those policies rather than reporting the username. If the user is editing in a biased or promotional way on a subject they appear to have a connection with, report them at the Conflict of Interest noticeboard.

Usernames for administrator attention guidelines
Usernames for administrator attention (UAA) is a noticeboard for drawing attention to abusive usernames quickly. See Usernames for administrator attention/Instructions for information on how to place or resolve UAA reports, including the options that are available to administrators.

Remember that blocking a new user is not actually something we want to do, it is something we do when it is needed to protect Wikipedia from harm. Generally, editors whose usernames are a technical or borderline violation of the Username policy should be given an opportunity to discuss the username and how they may register a new username. However, users who are reluctant to register a new username and are otherwise showing a positive history of contributions to Wikipedia should be allowed to continue editing in a positive fashion and the matter should be dropped. But this exemption does not apply to editors who have a clearly offensive username, disruptive or vandalizing edits, or edits that show a history of problematic bias or conflict of interest.

Real names
Minors and children are strongly discouraged from creating accounts with usernames that are their real names, or any nicknames which might be traced to them, and all editors should carefully consider the consequences before doing so. Usernames with this information significantly increase the potential for harassment, especially if these accounts edit in controversial subject areas. In some countries, editing Wikipedia can be illegal, and using your real name can put you at risk of legal consequences. While it is possible to rename your account later (see Changing your username below), a record of your previous username remains permanently.

Do not edit under a name that is likely to imply that you are (or are related to) a specific, identifiable person, unless it is your real name. If you have the same name as a well-known person to whom you are unrelated, and are using your real name, you should state clearly on your userpage that you are unrelated to the well-known person.

If a username implies that the user is, or is related to, a notable, identifiable or well-known person, the account may be blocked as a precaution against impersonation until the user's proof of identity is provided.

If you have been blocked for using your real name, please do not take offense; we are trying to prevent somebody from impersonating or harassing you, or someone you may share the same real name with. You are welcome to use your real name, but in some cases, you will need to prove that you are who you say you are. You can do this by sending an email to [mailto:info-en@wikimedia.org info-en@undefinedwikimedia.org]. Be aware that emails are handled by a volunteer response team; it can take some time before you'll receive a reply. Do not send unsolicited scans of your passport or driver's license to the volunteer response team. Instead, you should contact them to find out the best way to prove your identity. The best way will vary, but could be by using a mail address on a domain name that belongs to you.

Stage names
Users may use their stage name, pen name, or other nickname as their username, provided that it uniquely identifies a single person. This is not considered promotional, even if commercial performances or publications are made under such a name, unless the user makes promotional edits within Wikipedia about themselves, their projects, etc. However, a user may not use someone else's stage name as a username, as per the section of this page.

Usernames with non-Latin characters
Users with usernames in non-Latin script writing systems are welcome to edit Wikipedia. There is no requirement that usernames must be in English or that Latin script characters must be used. However, such usernames may appear illegible to other contributors to the English Wikipedia, and not every user's keyboard or input device may have immediate access to non-Latin characters. In addition, sometimes certain characters may not display correctly. As a courtesy to other contributors, and to avoid possible confusion or mis-identification, users with such usernames are encouraged to consider providing a Latin-character transliteration of their username on their userpage, and/or as their signature.

For technical reasons, usernames containing the forbidden characters, as well as  , are not possible.

Similar usernames
Usernames that are very similar to existing ones cannot be registered normally – but if you do want to use one, you may request its creation at Request an account. Usernames that are similar only to unused or inactive accounts should not be a problem. Special:CentralAuth can be used to check for such usernames. The program that checks for similarity is a bit over-sensitive—if the username is different enough as to prevent other people from confusing the two users, the request should be approved. One should not choose a username that implies a relationship with an existing editor (unless the account is actually owned or the relationship is acknowledged by the editor themselves).

If your username is similar to that of another contributor or an article, you may wish to provide some form of disambiguation, such as by adding distinguish to the top of your user page.

Commonly misspelled usernames
If your username is commonly misspelled, consider helping people by adding redirects to your actual user page and talk page from the misspelled titles. You may wish to consider registering the misspelled username as a doppelgänger account to prevent it from being registered by someone else. The software prevents registration of certain names that are found to be too similar to existing ones; if you cannot register your doppelgänger username for this reason, you should visit Request an account.

UseModWiki-era anonymous users
UseModWiki, the software used on Wikipedia throughout 2001 and in early 2002, treated users who edited without logging in or providing a screen name differently from modern-day MediaWiki. Anonymous users in that time were treated in one of two ways:
 * Domain names: Up until about March 2001, an editor with an IP address "192.0.2.34" that was associated with domain name "host.2.34.example.net" would have their edit logged as being by "host.2.34.example.net". Examples of this are office.bomis.com, dhcp-22-128.lclark.edu, and cnts2p46.uwaterloo.ca. Contributions by users with these usernames are affected by T2323. These usernames are usually indefinitely blocked on sight, as a) they don't make good usernames in light of the above criteria, b) they were never true usernames in the first place and would thus have been abandoned with changing software, and c) modern software is such that an innocent contributor editing from the "host.2.34.example.net" server would not be affected by a block of "User:host.2.34.example.net".
 * Redacted IP addresses: An editor with that same IP address that was not associated with any domain name (or all UseModWiki edits after about March 2001) would have their edit logged as being by "192.0.2.xxx". The Phase II software also exhibited this trait. Examples of this are 209.69.30.xxx and 62.110.183.xxx.

Shared accounts
Any user account should represent an individual and not a group (and an individual should normally only have one user account; see next section). Sharing an account – or the password to an account – with others is not permitted, and evidence of doing so will result in the user being required to stop the practice and change their password, or in sanctions (up to and including the account being blocked), depending on circumstances. For accounts being used to represent a group or organization, see and  above.

Exceptions to this rule can be made for non-editing accounts approved to provide email access, accounts approved by the Wikimedia Foundation (see list), and bot accounts that are maintained by more than one contributor, provided the existence of such an arrangement is made clear and has consensus.

Using multiple accounts
It is recommended that contributors not use multiple accounts without good reason. For example, a user may wish to create an alternate account for use on public computers as a precaution to keep their primary account more secure. Contributors operating any sort of automated editing process should do so under an alternative bot account. It is recommended that multiple accounts be identified as such on their user pages; templates such as User alternative account or one of a selection of user boxes may be used for this purpose.

The use of multiple accounts outside of established policy for doing so is known as sockpuppetry, and is not permitted. For example, multiple accounts may not be used to comment on proposals or requests, cast votes, or engage in edit warring. Because policies apply to individuals, not accounts, blocked or banned users must not use sock puppets to circumvent a block; doing so will result in an extension of the block or ban.

Changing your username
Usernames can be changed by global renamers; requests should be made at Changing username. User accounts with few or no edits might not be renamed, as it is quicker and easier to simply.

Once a username has been changed, existing contributions will be listed under the new name in page histories, diffs, logs, and user contributions. Signatures on discussion pages will continue to use the old name; while these can be changed manually, it is not recommended unless a contributor wishes to remove as much information as possible about their former name for privacy reasons. In such situations the old name will still be available in old versions of discussion pages, unless revision deletion is used and log entries are hidden from public view. Username changes are listed in the user rename log and the global rename log.

Deleting and merging accounts
It is not possible to delete user accounts, as all contributions must be assigned to some identifier, either a username or an IP address. Editors seeking privacy per courtesy vanishing / right to vanish can usually have their accounts renamed and their user pages (and, in exceptional cases, user talk pages) deleted.

It is not currently possible to merge more than one user account together and combine them into one user account on the English Wikipedia.

title: Wikipedia:Username policy


text:
Caucasia

Caucasia may refer to:
 * Caucasus, geographic region between the Black and Caspian Seas.
 * Caucasia, Antioquia, a municipality in Colombia
 * Caucasia (novel), a 1998 book by Danzy Senna
 * Caucasia (film), a 2007 Azerbaijani film directed by Farid Gumbatov

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Caucasia


text:
Hey, Slavs

"Hey, Slavs" is a patriotic song dedicated to the Slavs and widely considered to be the Pan-Slavic anthem. It was adapted and adopted as the national anthem of various Slavic-speaking nations, movements and organizations during the late 19th and 20th century.

Its lyrics were first written in 1834 under the title "Hey, Slovaks" ("Hej, Slováci") by Samo Tomášik and it has since served as the anthem of the Pan-Slavic movement, the organizational anthem of the Sokol movement, and the national anthems of the First Slovak Republic, Yugoslavia and Serbia and Montenegro. It was composed to the tune of "Mazurek Dąbrowskiego" from 1797, which was adopted as the national anthem of Poland in 1926, but the Yugoslav variation has a slower tempo, is more accentuated, and does not repeat the last four lines as it repeats the last two lines. The composer is unknown, although modern renditions of the song often used a World War II-era arrangement by Oskar Danon.

Etymology
In Serbo-Croatian, which uses both the Latin and the Cyrillic alphabets, the song had been titled as (in Croatian and in Serbian standard, respectively):
 * Hej, Slaveni or Hej, Sloveni (in Latin)
 * Хеј, Славени or Хеј, Словени (in Cyrillic)

In Macedonian the song's title is "Ej, Sloveni" (Cyrillic: Еј, Словени), and in Slovene, it is "Hej, Slovani". The original title in Slovak was "Hej, Slováci".

Slovakia
The song was written initially in Czech by the Slovak Lutheran minister Samuel Tomášik while he was visiting Prague in 1834. He was appalled that German was more commonly heard in the streets of Prague than Czech. He wrote in his diary:

 * "If mother Prague, the pearl of the Western Slavic world, is to be lost in a German sea, what awaits my dear homeland, Slovakia, which looks to Prague for spiritual nourishment? Burdened by that thought, I remembered the old Polish song Jeszcze Polska nie zginęła, kiedy my żyjemy ("Poland has not yet perished as long as we live."). That familiar melody caused my heart to erupt with a defiant Hej, Slováci, ešte naša slovenská reč žije ("Hey, Slovaks, our Slovak language still lives")... I ran to my room, lit a candle and wrote down three verses into my diary in pencil. The song was finished in a moment." (Diary of Samuel Tomášik, Sunday, 2 November 1834)

Tomášik left the instructions for his song to be performed to the melody of Dąbrowski's Mazurka: "It be sung as: Poland has not yet perished".

He soon altered the lyrics to include all Slavs and "Hey, Slavs" became a widely known rallying song for Slav nationalism and Pan-Slavic sentiment, especially in the West Slavic lands governed by Austria. It was printed in numerous magazines and calendars and sung at political gatherings, becoming an unofficial anthem of the Pan-Slavic movement.

Its popularity continued to increase when it was adopted as the organizational anthem of the Sokol ("falcon") physical education movement, which was based on Pan-Slavic ideals and active across Austria-Hungary. In 1905, the erection of a monument to the Slovene poet France Prešeren in Ljubljana was celebrated by a large gathering of people singing "Hey, Slavs". During the First World War, the song was often used by Slavic soldiers from opposite sides of the front line to communicate common nationalist sentiment and prevent bloodshed.

In Slovakia, the song "Hey, Slovaks" has been considered the unofficial ethnic anthem of the Slovaks throughout its modern history, especially at times of revolution. Although after the First World War the song "Nad Tatrou sa blýska" became the official Slovak part in the national anthem of Czechoslovakia and then again in 1993 in anthem of independent Slovakia, "Hey, Slovaks" is still considered a "second" national anthem by many (usually more nationalistic) people. Contrary to popular assumption, there was no official state anthem of the clerofascist Slovak Republic (1939–45), though "Hej, Slováci" was used by the ruling party.

Yugoslavia
The first appearance of "Hey, Slavs" in Yugoslavia was during the Illyrian movement. Dragutin Rakovac translated the song, naming it "Hey, Illyrians" (Hej, Iliri). Until the Second World War, the translation did not undergo many changes, except that the Illyrians became Slavs.

In 1941 the Second World War engulfed the Kingdom of Yugoslavia. The Axis powers invaded in early April, and the Yugoslav royal army disintegrated and capitulated in just two and a half weeks. Since the old Yugoslav anthem included references to king and kingdom, the anti-royalist Partisan resistance led by Josip Broz Tito and his Communist party decided to avoid it and opted for "Hey, Slavs" instead. The song was sung at both the first and second sessions of AVNOJ, the legislative body of the resistance, and it gradually became the de facto national anthem of Democratic Federal Yugoslavia (new Yugoslavia).

The old state anthem was officially abandoned after liberation in 1945, but no new national anthem to replace it was officially adopted. There were several attempts to promote other, more specifically Yugoslav songs as the national anthem, but none gained much public support and "Hey, Slavs" continued to be used unofficially. The search for a better candidate continued up to 1988, while in 1977 the law only named the national anthem as "Hey, Slavs" as a temporary state anthem until a new one was adopted, which never happened.

"Hey, Slavs" under its Serbo-Croatian title "Hej, Slaveni" was therefore the national anthem of Yugoslavia for a total of 48 years, from 1943 to 1992. With the formal adoption (inauguration) of Amendment IX to the Constitution of the Socialist Federal Republic of Yugoslavia, the song "Hey, Slavs" gained constitutional sanction as the national anthem on November 25, 1988. After 43 years of continued use as the de facto national anthem, the delegates simply brought the law in line with custom.

Serbia and Montenegro
After the break-up of Yugoslavia in 1991 and 1992, when only Serbia and Montenegro remained in the federation, "Hey, Slavs" continued to be used, as the national anthem of the Federal Republic of Yugoslavia (FRY). Slobodan Milošević wanted to adopt “Hey, Slavs” as the Serbian anthem, but the Main Board of the Socialist Party of Serbia overruled it, feeling that it was inappropriate to reuse it after having assigned it to Yugoslavia, thus they assigned Serbia “March on the Drina” instead. The FRY was renamed to the State Union of Serbia and Montenegro in 2003 and was expected to adopt a new national anthem, but since no agreement over state symbols could be reached, "Hey, Slavs" remained the national anthem of the state. Many Serbs disliked the song during this period and booed it whenever it was played, such as at sporting events and football games.

A hybrid of the Montenegrin folk song (now national anthem) "Oj, svijetla majska zoro" with the former (now current) Serbian national anthem, "Bože Pravde" in alternating verses was proposed (similarly to Czechoslovakia, whose anthem consisted of the Czech part "Kde domov můj" and the Slovak part "Nad Tatrou sa blýska"). However, this attempt was struck down after objections by the People's Party of Montenegro and the Socialist People's Party of Montenegro. Also proposed was the former Montenegrin national anthem and patriotic song "Onamo, 'namo", however this also fell through and "Hey, Slavs" remained the national anthem. Since Montenegro and Serbia dissolved their union and split to become sovereign states in 2006, this issue is moot, as "Hey, Slavs" is no longer used as an official national anthem by any sovereign state. In a way, "Hey, Slavs" ended up outliving the countries that used it, as the last instance of it being officially played as part of an event was at the 2006 FIFA World Cup, where the Serbia and Montenegro national football team participated despite the country they were playing for no longer existing (having disbanded a few days before the tournament began).

Even after the end of the federation, "Hey, Slavs" was sometimes still mistakenly played by organizers of sports events that involve Serbian teams as a guest side. Notable performances, some of which were intentional, include the 2013 UEFA U-19 Championship semi-final football match between Serbia and Portugal as well as the Olympiacos–Partizan ULEB Champions league basketball game in 2010. In 2015, French organizers of 2015 European Touring Car Cup season erroneously played "Hey, Slavs" when Serbian racing driver Dušan Borković won 1st place at Circuit Paul Ricard.

In popular culture
The Yugoslav band Bijelo Dugme recorded a version of the song for their 1984 self-titled album. The Yugoslav and Slovenian band Laibach recorded an electronic version of the song, with lyrics in both English and Slovene, for their 2006 album Volk. The song is also featured in the 2002 Slovenian film Headnoise.

title: Hey, Slavs


text:
Transmeta

Transmeta Corporation was an American fabless semiconductor company based in Santa Clara, California. It developed low power x86 compatible microprocessors based on a VLIW core and a software layer called Code Morphing Software.

Code Morphing Software (CMS) consisted of an interpreter, a runtime system and a dynamic binary translator. x86 instructions were first interpreted one instruction at a time and profiled, then depending upon the frequency of execution of a code block, CMS would progressively generate more optimized translations.

The VLIW core implemented features specifically designed to accelerate CMS and translations. Among the features were support for general speculation, detection of memory aliasing and detection of self modifying x86 code.

The combination of CMS and the VLIW core allowed for the achievement of full x86 compatibility while maintaining performance and reducing power consumption.

Transmeta was founded in 1995 by Bob Cmelik, Dave Ditzel, Colin Hunter, Ed Kelly, Doug Laird, Malcolm Wing and Greg Zyner.

Its first product, the Crusoe processor, was launched on January 19, 2000. Transmeta went public on November 7, 2000. On October 14, 2003, it launched its second major product, the Efficeon processor. In 2005, Transmeta increased its focus on licensing its portfolio of microprocessor and semiconductor technologies. After layoffs in 2007, Transmeta made a complete shift away from semiconductor production to IP licensing. In January 2009, the company was acquired by Novafora and the patent portfolio was sold to Intellectual Ventures. Novafora ceased operations in August 2009. Intellectual Ventures licenses the Transmeta IP to other companies on a non-exclusive basis.

Transmeta produced two x86 compatible CPU architectures: Crusoe and Efficeon – internal code names were 'Fred' and 'Astro'. These CPUs have appeared in subnotebooks, notebooks, desktops, blade servers, tablet PCs, a personal cluster computer, and a silent desktop, where low power consumption and heat dissipation are of primary importance.

Before the 2009 acquisition by Novafora, Transmeta had moderate success licensing its IP. Licensors for Transmeta technology are Intel (with a perpetual, non-exclusive license to all Transmeta patents and patent applications, including any that Transmeta might acquire before December 31, 2017), Nvidia (with non-exclusive license to Transmeta's LongRun and LongRun2 technologies and other intellectual property), Sony (LongRun2 licensee), Fujitsu (LongRun2 licensee) and NEC (LongRun2 licensee).

Stealth mode
Founded in 1995, Transmeta began as a stealth start-up. The company was largely successful in hiding its ambitions until its official company launch on January 19, 2000. Over 2000 non-disclosure agreements (NDAs) were signed during the stealth period. Throughout Transmeta's first few years, little was known about exactly what it would be offering. Its web site went online in mid 1997 and for approximately two and a half years displayed nothing but the text, "This web page is not yet here."

On November 12, 1999, a cryptic comment in the HTML appeared: Yes, there is a secret message, and this is it: Transmeta's policy has been to remain silent about its plans until it had something to demonstrate to the world. On January 19, 2000, Transmeta is going to announce and demonstrate what Crusoe processors can do. Simultaneously, all of the details will go up on this Web site for everyone on the Internet to see. Crusoe will be cool hardware and software for mobile applications. Crusoe will be unconventional, which is why we wanted to let you know in advance to come look at the entire Web site in January, so that you can get the full story and have access to all of the real details as soon as they are available.

Transmeta attempted to staff the company in secret although speculation online was not uncommon. Information gradually came out of the company suggesting it was working on a very long instruction word (VLIW) design that translated x86 code into its own native VLIW code.

Open for business
On January 19, 2000, Transmeta held a launch event at Villa Montalvo in Saratoga, California and announced to the world that it had been working on an x86 compatible dynamic binary translation processor named Crusoe. It also released an 18-page whitepaper describing the technology.

Transmeta marketed their microprocessor technology as extraordinarily innovative and revolutionary in the low-power market segment. They had hoped to be both power and performance leaders in the x86 space but initial reviews of Crusoe indicated the performance fell significantly short of projections. Also, while Crusoe was in development, Intel and AMD significantly ramped up speeds and began to address concerns about power consumption. So Crusoe was rapidly cornered into a low-volume, small form factor (SFF), low-power segment of the market.

On November 7, 2000 (US election day), Transmeta had their initial public offering at the price of $21 a share. The value reached a high of $50.26 before settling down to $46 a share on opening day. This made Transmeta the last of the great high tech IPOs of the dot-com bubble. Their opening day performance would not be surpassed until Google’s IPO in 2004.

The company had its first layoffs in July 2002, reducing the headcount of the company by 40%.

On October 14, 2003, Transmeta announced the Efficeon processor which was claimed to have twice the performance of the original Crusoe CPU at the same frequency. However, performance was still weak relative to the competition and the complexity of the chip had increased significantly. The greater size and power consumption may have diluted a key market advantage Transmeta's chips had previously enjoyed over the competition.

In January 2005, the company announced its first strategic restructuring away from being a semiconductor product company and began to focus on licensing intellectual property. In March 2005, Transmeta announced that it was laying off 68 people while retaining 208 employees. Sony was reported to be a key licensee of Transmeta technology and approximately half of the remaining employees were to work on LongRun2 power optimization technology for Sony.

On May 31, 2005, Transmeta announced the signing of asset purchase and license agreements with Hong Kong’s Culture.com Technology Limited. The deal fell apart due to delays in obtaining technology export licenses from the US Department of Commerce and the parties announced the termination of the agreements on February 9, 2006.

On August 10, 2005, Transmeta announced its first-ever profitable quarter. This was followed by GameSpot’s March 20, 2006 report that Transmeta was working on an “unnamed” Microsoft project. As it turned out, this was a secure platform under the AMD brand for Microsoft's FlexGo program.

On October 11, 2006, Transmeta announced that they had filed a lawsuit against Intel Corporation for infringement of ten Transmeta U.S. patents covering computer architecture and power efficiency technologies. The complaint charged that Intel had infringed and was infringing Transmeta's patents by making and selling a variety of microprocessor products, including at least Intel's Pentium III, Pentium 4, Pentium M, Core and Core 2 product line.

On February 7, 2007, Transmeta shut down its engineering services division terminating 75 employees in the process. This was concurrent with an announcement that the company would no longer develop and sell hardware and would focus on the development and licensing of intellectual property. Subsequently, AMD invested $7.5 million in Transmeta, planning to use the company's patent portfolio in energy-efficient technologies.

On October 24, 2007, Transmeta announced an agreement to settle its lawsuit against Intel Corporation. Intel agreed to pay $150 million upfront and $20 million per year for five years to Transmeta in addition to dropping its counterclaims against Transmeta. Transmeta also agreed to license several of its patents and assign a small portfolio of patents to Intel as part of the deal. Transmeta also agreed to never manufacture x86 compatible processors again. One significant sore point in the Intel litigation was the payout of approximately $34M to three of Transmeta's executives. In late 2008, Intel and Transmeta reached a further agreement to transfer the $20 million per year in one lump sum.

On August 8, 2008, Transmeta announced that it had licensed its LongRun and low power chip technologies to Nvidia for a one time license fee of $25 million. On November 17, Transmeta announced the signing of a definitive agreement to be acquired by Novafora, a digital video processor company based in Santa Clara, California, for $255.6 million in cash, subject to adjustments dependent on working capital. The deal was finalized on January 28, 2009, when Novafora announced the completion of its acquisition of Transmeta.

Intellectual Venture Funding LLC completed the acquisition of the patent portfolio formerly developed and owned by Transmeta Corporation on February 4, 2009.

Due to financial troubles and inability to execute, Novafora collapsed in late July, 2009.

Corporate governance
Transmeta had a succession of 6 different chief executive officers who ran the company over its lifetime.

Notable employees
Among its crew of technologists, Transmeta employed some of the industry's more public figures including Linux founder Linus Torvalds, Linux kernel developer Hans Peter Anvin, Yacc author Stephen C. Johnson, and game developer Dave D. Taylor. Partially because of the presence of these figures, the industry was constantly abuzz with rumors and 'conspiracy theories' resulting in excellent press relations.

Financial history
The following charts show the company's revenues, operating expenses, gross profits and net losses from 1996 through 2007. Numbers are in 1000s as per the 10-K reports. The company was once named as the Most important company in Silicon Valley in an Upside magazine editorial but failed to obtain profitability while it was a chip vendor.

Funding
Transmeta received a total of $969M in funding during its lifetime.

Crusoe
Crusoe was the first family of microprocessors from Transmeta, named after the literary character Robinson Crusoe.

Transmeta lost much credibility and endured significant criticism due to the large discrepancies between projected performance and power consumption and the actual results. Although power consumption was somewhat better than Intel and AMD offerings, the end user experience (i.e. battery life) only showed a marginal overall improvement. First, the Code Morphing Software (CMS) combined with cache architecture artificially inflated comparisons between benchmarks and real-world applications. This is due to the repetitive nature of benchmarks and their small footprints. The CMS software overhead may have actually been a key cause of much lower performance for many real-world applications; the simple VLIW core architecture could not compete on computationally intensive applications; and the southbridge interface was limited by its low bandwidth for graphics or other I/O-intensive applications. Some standard benchmarks even failed to run, throwing the claim of full x86 compatibility into doubt.

Efficeon
The Efficeon processor was Transmeta's second-generation 256-bit VLIW processor design. Like the Crusoe (a 128-bit VLIW architecture), Efficeon stressed computational efficiency, low power consumption, and a low thermal footprint.

A 2004-model 1.6-GHz Transmeta Efficeon (manufactured using a 90 nm process) had roughly the same performance and power characteristics as a 1.6-GHz Intel Atom from 2008 (manufactured using a 45 nm process). The Efficeon included an integrated Northbridge, while the competing Atom required an external Northbridge chip, reducing much of the Atom's power consumption benefits.

The Transmeta Efficeon processor addressed many of Crusoe's shortcomings and showed roughly a 2x real-world improvement over Crusoe. Its die was considerably smaller than Pentium 4 and Pentium M, when compared in the same process technology. Efficeon's die fabricated in 90 nm is 68 mm2, which is 60% of the Pentium 4 in 90 nm, at 112 mm2, with both processors possessing a 1 MB L2 cache.

The notion of selling a product into a specific thermal envelope was typically not understood by the mass of reviewers, who tended to compare Efficeon to the gamut of x86 microprocessors, regardless of power consumption or application. One such example of this criticism suggests the performance still significantly lagged behind Intel's Pentium M (Banias) and AMD's Mobile Athlon XP.

Technology
Transmeta processors were in-order very long instruction word (VLIW) cores running a special dynamic binary translation software layer which together implemented compatibility with the x86 architecture. Transmeta trademarked the term "Code Morphing" to describe their technology and referred to the software layer as Code Morphing Software (CMS).

Transmeta used reverse body bias to reduce power used by a factor of about 2.5. (A similar technology was used in XScale processors.)

Code Morphing Software
Code Morphing Software (CMS) is the technology used by Transmeta microprocessors to execute x86 instructions. In broad view, CMS reads x86 instructions and generates instructions for a proprietary VLIW processor, in the style of Shade. CMS translation is much more expensive than Shade's, but produces much higher quality code. CMS also contains an interpreter and simulates both user-mode and system mode operation.

Code Morphing Software consisted of an interpreter, a runtime system and a dynamic binary translator. x86 instructions were first interpreted one instruction at a time and profiled, then depending upon the frequency of execution and other heuristics, CMS would progressively generate more optimized translations.

Similar technologies existed in the 1990s: Wabi for Solaris and Linux, FX!32 for Alpha and IA-32 EL for Itanium, open-source DAISY, the Mac 68K emulator for the PowerPC. The Transmeta approach set a much higher bar for x86 compatibility due to its ability to execute all x86 instructions from initial boot up to the latest multimedia instructions.

The operation of Transmeta's code morphing software is similar to the final optimization pass of a conventional compiler. Considering a fragment of 32-bit x86 code:

add eax,dword ptr [esp] // load data from stack, add to eax add ebx,dword ptr [esp] // ditto, for ebx mov esi,[ebp]          // load esi from memory sub ecx,5              // subtract 5 from ecx register

This is first converted simplistically into native instructions:

ld %r30,[%esp]      // load from stack, into temporary add.c %eax,%eax,%r30 // add to %eax, set condition codes. ld %r31,[%esp] add.c %ebx,%ebx,%r31 ld %esi,[%ebp] sub.c %ecx,%ecx,5

The optimizer then eliminates common sub-expressions and unnecessary condition code operations and, potentially, applies other optimizations such as loop unrolling:

ld %r30,[%esp]    // load from stack only once add %eax,%eax,%r30 add %ebx,%ebx,%r30 // reuse data loaded earlier ld %esi,[%ebp] sub.c %ecx,%ecx,5 // only this last condition code needed

Finally, the optimizer groups individual instructions ("atoms") into long instruction words ("molecules") for the underlying hardware:

ld %r30,[%esp]; sub.c %ecx,%ecx,5 ld %esi,[%ebp]; add %eax,%eax,%r30;  add %ebx,%ebx,%r30

These two VLIW molecules could potentially execute in fewer cycles than the original instructions could on an x86 processor.

Transmeta claimed several technical benefits to this approach:
 * 1) As the market leaders Intel and/or AMD would extend the core x86 instruction set, Transmeta could quickly upgrade their product with a software upgrade rather than requiring a respin of their hardware.
 * 2) Performance and power can be tuned in software to meet market needs.
 * 3) It would be relatively simple to fix hardware design or manufacturing flaws in the hardware using software workarounds.
 * 4) More time could be spent concentrating on enhancing the capabilities of the core or reducing its power consumption without worrying about 33 years of backward compatibility to the x86 architecture.
 * 5) The processor could emulate multiple other architectures, possibly even at the same time. (At its initial Crusoe launch, Transmeta demonstrated pico-Java and x86 running intermixed on the native hardware.)

Prior to Crusoe's release, rumors indicated Transmeta was relying on these benefits to develop a hybrid PowerPC and x86 processor. But Transmeta would initially concentrate solely on the extremely low-power x86 market.

The ability to quickly update products without a hardware respin was demonstrated in 2002 with an in-the-field upgrade (a download) to enhance CPU performance of the Crusoe based HP Compaq TC1000 tablet PC. It was used again in 2004 when NX bit and SSE3 support were added to the Transmeta Efficeon product line without requiring hardware changes. In the field upgrades were rare in practice due to system hardware vendors not wanting to incur additional customer support costs or spend additional money on QA for the potential upgrades or bug fixes to shipped products they had already closed the revenue books on.

VLIW core
In conjunction with its code-morphing software the Efficeon most closely mirrors the feature set of Intel Pentium 4 processors, although, like AMD Opteron processors, it supports a fully integrated memory controller, a HyperTransport IO bus, and the NX bit, or no-execute x86 extension to PAE mode. NX bit support is available starting with CMS version 6.0.4.

Efficeon's computational performance relative to mobile CPUs like the Intel Pentium M is thought to be lower, although little appears to be published about the relative performance of these competing processors.

Efficeon came in two package types: a 783- and a 592-contact ball grid array. Its power consumption was moderate (with some consuming as little as 3 watts at 1 GHz and 7 watts at 1.5 GHz), so it could be passively cooled.

Two generations of this chip were produced. The first generation (TM8600) was manufactured using a TSMC 130 nm process and produced at speeds up to 1.1 GHz. The second generation (TM8800 and TM8820) was manufactured using a Fujitsu 90 nm process and produced at speeds ranging from 1 GHz to 1.7 GHz.

Internally, the Efficeon had two arithmetic logic units, two load/store/add units, two execute units, two floating-point/MMX/SSE/SSE2 units, one branch prediction unit, one alias unit, and one control unit. The VLIW core could execute a 256-bit VLIW instruction per cycle. A VLIW is called a molecule and has room to store eight 32-bit instructions (called atoms) per cycle.

The Efficeon had a 128-KB L1 instruction cache, a 64-KB L1 data cache and a 1-MB L2 cache. All caches were on die.

Additionally, Efficeon code morphing software (CMS) reserved a small portion of main memory (typically 32 MB) for its cache of dynamically translated x86 instructions.

Native compilation
In principle, it should be possible to optimize x86 code to favor Code Morphing Software, or even for compilers to target the native VLIW architecture directly. However, writing in 2003, Linus Torvalds apparently dismissed these approaches as unrealistic:

"The native crusoe code – even if it was documented and available – is not very conducive to general-purpose OS stuff. It has no notion of memory protection, and there's no MMU for code accesses, so things like kernel modules simply wouldn't work.

The translations are usually better than statically compiled native code (because the whole CPU is designed for speculation, and the static compilers don't know how to do that), and thus going to native mode is not necessarily a performance improvement.

So no, it wouldn't really benefit from it, not to mention that it's not even an option since Transmeta has never released enough details to do it anyway. Largely for simple security concerns – if you start giving interfaces for mucking around with the "microcode", you could do some really nasty things.

[...I meant...] "you cannot do that". And we won't even tell the details of how you cannot do that.

In fact, even inside transmeta you cannot do that, without having a specially blessed version of the flash that allows upgrades. If you ever see a machine with a prominent notice saying "CMS upgraded to development version", then that's a hint that it's a machine that TMTA developers could change."

- Linus Torvalds

Subsequent reverse engineering, published in 2004, clarifies some details of the native VLIW architecture and associated instruction set, and suggests that there are fundamental limitations that preclude porting an operating system such as Linux to it.

The same work also compares Transmeta's patented technology with prior art published and in some cases patented by IBM, and suggests that some claims might not stand detailed scrutiny.

title: Transmeta


text:
Wikipedia:Historical archive/Common words, searching for which is not possible

'As of February 2006, the information on this page is no longer correct. Wikipedia's current Lucene index does not use "stop words", so any word can be successfully used in search queries.'

Some words in wikipedia cannot currently be searched for, because they are deemed too common. The following is a full list of those words. They are written as links, so that at least articles with a single common word as title can be found through this list.

If the exact title of an article is known or guessed, the Go button can be used; this feature is not affected by the above-mentioned restriction.

Further articles which are difficult to find otherwise:
 * Years: 1 2 3 4 5 6 7 8 9

 * E.T.
 * Just Like That

Search Wikipedia with Google (based on contents of about a month ago!)

Search Wikipedia with Clusty (may be more up to date)

 * 1-1
 * a
 * a's
 * able
 * about
 * above
 * according
 * accordingly
 * across
 * actually
 * after
 * afterwards
 * again
 * against
 * ain't
 * all
 * allow
 * allows
 * almost
 * alone
 * along
 * already
 * also
 * although
 * always
 * am
 * among
 * amongst
 * an
 * and
 * another
 * any
 * anybody
 * anyhow
 * anyone
 * anything
 * anyway
 * anyways
 * anywhere
 * apart
 * appear
 * appreciate
 * appropriate
 * are
 * aren't
 * around
 * as
 * aside
 * ask
 * asking
 * associated
 * at
 * available
 * away
 * awfully
 * b
 * be
 * became
 * because
 * become
 * becomes
 * becoming
 * been
 * before
 * beforehand
 * behind
 * being
 * believe
 * below
 * beside
 * besides
 * best
 * better
 * between
 * beyond
 * both
 * brief
 * but
 * by
 * c
 * c'mon
 * c's
 * came
 * can
 * can't
 * cannot
 * cant
 * cause
 * causes
 * certain
 * certainly
 * changes
 * clearly
 * co
 * com
 * come
 * comes
 * concerning
 * consequently
 * consider
 * considering
 * contain
 * containing
 * contains
 * corresponding
 * could
 * couldn't
 * course
 * currently
 * d
 * definitely
 * described
 * despite
 * did
 * didn't
 * different
 * do
 * does
 * doesn't
 * doing
 * don't
 * done
 * down
 * downwards
 * during
 * e
 * each
 * edu
 * eg
 * eight
 * either
 * else
 * elsewhere
 * enough
 * entirely
 * especially
 * et
 * etc
 * even
 * ever
 * every
 * everybody
 * everyone
 * everything
 * everywhere
 * ex
 * exactly
 * example
 * except
 * f
 * far
 * few
 * fifth
 * first
 * five
 * followed
 * following
 * follows
 * for
 * former
 * formerly
 * forth
 * four
 * from
 * further
 * furthermore
 * g
 * get
 * gets
 * getting
 * given
 * gives
 * go
 * goes
 * going
 * gone
 * got
 * gotten
 * greetings
 * h
 * had
 * hadn't
 * happens
 * hardly
 * has
 * hasn't
 * have
 * haven't
 * having
 * he
 * he's
 * hello
 * help
 * hence
 * her
 * here
 * here's
 * hereafter
 * hereby
 * herein
 * hereupon
 * hers
 * herself
 * hi
 * him
 * himself
 * his
 * hither
 * hopefully
 * how
 * howbeit
 * however
 * i
 * i'd
 * i'll
 * i'm
 * i've
 * ie
 * if
 * ignored
 * immediate
 * in
 * inasmuch
 * inc
 * indeed
 * indicate
 * indicated
 * indicates
 * inner
 * insofar
 * instead
 * into
 * inward
 * is
 * isn't
 * it
 * it'd
 * it'll
 * it's
 * its
 * itself
 * j
 * k
 * keep
 * keeps
 * kept
 * know
 * knows
 * known
 * l
 * last
 * lately
 * later
 * latter
 * latterly
 * least
 * less
 * lest
 * let
 * let's
 * like
 * liked
 * likely
 * little
 * look
 * looking
 * looks
 * ltd
 * m
 * mainly
 * many
 * may
 * maybe
 * me
 * mean
 * meanwhile
 * merely
 * might
 * more
 * moreover
 * most
 * mostly
 * much
 * must
 * my
 * myself
 * n
 * name
 * namely
 * nd
 * near
 * nearly
 * necessary
 * need
 * needs
 * neither
 * never
 * nevertheless
 * new
 * next
 * nine
 * no
 * nobody
 * non
 * none
 * noone
 * nor
 * normally
 * not
 * nothing
 * novel
 * now
 * nowhere
 * o
 * obviously
 * of
 * off
 * often
 * oh
 * ok
 * okay
 * old
 * on
 * once
 * one
 * ones
 * only
 * onto
 * or
 * other
 * others
 * otherwise
 * ought
 * our
 * ours
 * ourselves
 * out
 * outside
 * over
 * overall
 * own
 * p
 * particular
 * particularly
 * per
 * perhaps
 * placed
 * please
 * plus
 * possible
 * presumably
 * probably
 * provides
 * q
 * que
 * quite
 * qv
 * r
 * rather
 * rd
 * re
 * really
 * reasonably
 * regarding
 * regardless
 * regards
 * relatively
 * respectively
 * right
 * s
 * said
 * same
 * saw
 * say
 * saying
 * says
 * second
 * secondly
 * see
 * seeing
 * seem
 * seemed
 * seeming
 * seems
 * seen
 * self
 * selves
 * sensible
 * sent
 * serious
 * seriously
 * seven
 * several
 * shall
 * she
 * should
 * shouldn't
 * since
 * six
 * so
 * some
 * somebody
 * somehow
 * someone
 * something
 * sometime
 * sometimes
 * somewhat
 * somewhere
 * soon
 * sorry
 * specified
 * specify
 * specifying
 * still
 * sub
 * such
 * sup
 * sure
 * t
 * t's
 * take
 * taken
 * tell
 * tends
 * th
 * than
 * thank
 * thanks
 * thanx
 * that
 * that's
 * thats
 * the
 * their
 * theirs
 * them
 * themselves
 * then
 * thence
 * there
 * there's
 * thereafter
 * thereby
 * therefore
 * therein
 * theres
 * thereupon
 * these
 * they
 * they'd
 * they'll
 * they're
 * they've
 * think
 * third
 * this
 * thorough
 * thoroughly
 * those
 * though
 * three
 * through
 * throughout
 * thru
 * thus
 * to
 * together
 * too
 * took
 * toward
 * towards
 * tried
 * tries
 * truly
 * try
 * trying
 * twice
 * two
 * u
 * un
 * under
 * unfortunately
 * unless
 * unlikely
 * until
 * unto
 * up
 * upon
 * us
 * use
 * used
 * useful
 * uses
 * using
 * usually
 * v
 * value
 * various
 * very
 * via
 * viz
 * vs
 * w
 * want
 * wants
 * was
 * wasn't
 * way
 * we
 * we'd
 * we'll
 * we're
 * we've
 * welcome
 * well
 * went
 * were
 * weren't
 * what
 * what's
 * whatever
 * when
 * whence
 * whenever
 * where
 * where's
 * whereafter
 * whereas
 * whereby
 * wherein
 * whereupon
 * wherever
 * whether
 * which
 * while
 * whither
 * who
 * who's
 * whoever
 * whole
 * whom
 * whose
 * why
 * will
 * willing
 * wish
 * with
 * within
 * without
 * won't
 * wonder
 * would
 * wouldn't
 * x
 * y
 * yes
 * yet
 * you
 * you'd
 * you'll
 * you're
 * you've
 * your
 * yours
 * yourself
 * yourselves
 * z
 * zero


text:
Wikipedia talk:Username policy

WT:UAA archives:
 * Wikipedia talk:Usernames for administrator attention/Archive 1
 * Wikipedia talk:Usernames for administrator attention/Archive 2
 * Wikipedia talk:Usernames for administrator attention/Archive 3
 * Wikipedia talk:Usernames for administrator attention/Archive 4
 * Wikipedia talk:Usernames for administrator attention/Archive 5
 * Wikipedia talk:Usernames for administrator attention/Archive 6
 * Wikipedia talk:Usernames for administrator attention/Archive 7

Wikipedia talk:Requests for comment/User names archives and deletion notices:

 * Wikipedia talk:Requests for comment/User names/Archive 1
 * Wikipedia talk:Requests for comment/User names/Archive 2
 * Wikipedia talk:Requests for comment/User names/Archive 3
 * Wikipedia talk:Requests for comment/User names/Archive 4
 * Wikipedia talk:Requests for comment/User names/Archive 5
 * Wikipedia talk:Requests for comment/User names/Archive 6

2014 Request for Comment on reforming and updating this policy

Wikipedia:Username policy/RFC 2024 has an RfC
Wikipedia:Username policy/RFC 2024 has an RfC for possible consensus. A discussion is taking place. If you would like to participate in the discussion, you are invited to add your comments on the |discussion page. Thank you. thetechie@enwiki :  ~/talk/  $  01:57, 1 May 2024 (UTC)
 * Discussion has been closed as premature. Primefac (talk) 12:46, 1 May 2024 (UTC)
 * It has been a decade since the last major RFC on the username policy, it might not be a bad idea to consider putting together something more comprehensive like the 2014 RFC. Just Step Sideways from this world ..... today 02:31, 9 May 2024 (UTC)
 * Probably. I will note that there have been changes made since that last reform, but they probably fall more under "tweaks" than "overhauls" (e.g. no emojis in 2017). Primefac (talk) 11:12, 9 May 2024 (UTC)

Titles as potential violations of username policy
Does the use of legally protected titles such as "Dr.", "doctor," "dentist," "surgeon," "lawyer," "engineer" and "architect," which require licensure or sufficient education, violate username policy when the user is not legally entitled to describe themselves as such? One issue besides the law is that these imply a level of professional knowledge that might give them an advantage in a content dispute. In a similar vein, "professor" might be part of this list, though it is not a protected occupational title as far as my knowledge goes. Air on White (talk) 22:17, 25 May 2024 (UTC) edited Air on White (talk) 00:27, 26 May 2024 (UTC)
 * Let's see, I can call myself "doctor" or "Dr.", as I have an earned PhD. I used to listen to Dr. Demento's radio show. "Engineer" is commonly used to describe someone who operates a locomotive. "Software engineer" is a common job title. We can call someone an "architect of ..." without them holding a specific degree or license. I do not see any legal restraint on someone using one of those titles in a username. We have had users who claimed expertise and qualifications that they did not actually have. Things have not always gone well for them when they were found out. But that was because of what they falsely and explicitly claimed, not because of some title they used in their username. Donald Albury 00:25, 26 May 2024 (UTC)
 * A straight-up violation, no. As Donald says, there are many times when it could be used with humour or otherwise without intending to "give an advantage". Someone claiming to be an expert and not actually being one is usually quickly shut down anyway, but WP:RFCN is always available if there are issues. Primefac (talk) 11:47, 26 May 2024 (UTC)
 * I don't believe Dr. Dre holds a PhD, nor Dr. J; the licensing issue refers to attempting to practice, not merely identifying one's self. Fairly sure if there were legal issues with people identifying themselves as a "doctor" the Foundation would have told us by now. 331dot (talk) 15:23, 26 May 2024 (UTC)

Editing Bot-reported usernames?
The bots are pretty good, but you do occasionally see false-positives sneak in. Is it appropriate for non-admin editors to edit the list and remove the ones they feel are not problematic? Or do admins need to do that (such as adding the username to a whitelist or something of the sort). For example, User:CharaIOnlyMadeThisToFixOneError was reported by a bot. Their one edit was non-controversial and there's nothing really problematic about the username (it was triggered by having a long number of characters without a space). As an uninvolved non-admin, could I just wipe that out? Matt Deres (talk) 20:15, 31 May 2024 (UTC)

 * Point #7 in the UAA instructions says Patrollers are asked to remove reports that [...] are bot-reported false positives, so feel free to remove bot reports if you're confident that they're false positives (like the one you mentioned). DanCherek (talk) 20:20, 31 May 2024 (UTC)
 * Since I have over 300 edits at UAA/Bot I can say from personal experience that non-admins are welcome. But be sure to check the accounts for other issues as well. Block evasion, LTA, vandalism-only, spam-only are common issues with the accounts that show up there. Nobody  ( talk ) 07:18, 3 June 2024 (UTC)

Discussion at Wikipedia:Bots/Noticeboard § HBC AIV helperbot5 and AdminStatsBot
You are invited to join the discussion at Wikipedia:Bots/Noticeboard § HBC AIV helperbot5 and AdminStatsBot.  This is related to the bot that clerks WP:UAA. – Novem Linguae (talk) 14:26, 18 July 2024 (UTC)

title: Wikipedia talk:Username policy


text:
Wikipedia talk:Historical archive/Common words, searching for which is not possible

Outdated?
With the new Lucene search this page seems to have been invalidated? --Dittaeva 09:10, 23 Jun 2005 (UTC)

Old talk
Which means that searching for, say, Lily Brett's novel Just Like That is impossible. Is this page just presenting the status quo or intended to trigger changes? --KF 14:27 Jan 13, 2003 (UTC)

 * Presenting the status quo. I agree that improvements are needed. - Patrick 14:33 Jan 13, 2003 (UTC)

 * I see. But you've already done a very good job by (a) creating this page and (b) linking it to both Help and Searching. --KF 14:39 Jan 13, 2003 (UTC)

 * Another example is a short film produced by South Park's Matt Stone and Trey Parker, called Your Studio And You, in which Steven Spielberg and other bigtime directors made cameo appearances mocking certain annoyances of movie production bureaucracy. I believe it was one of their pre-South Park era creations, actually.  Doubt Wikipedia has an article on it anyway, but just try looking up information on Google for that film.  Every webpage in existence with the word "studio", instead, will be presented to you. --I run like a Welshman 11:35, 8 Dec 2004 (UTC)

These seem like common words, but I was curious how they were determined. Were they based on a word frequency corpus, or were they simply derived intuitively? I was wondering because, if they were derived systematically, this might be a useful list to use at http://wiktionary.org as a template for making lists of common words in other languages. We set up such a page for Basic English words already, but I was thinking this list might also be useful. Thanks. - Brettz9 03:48 Apr 22, 2003 (UTC)

 * I took them from http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/wikipedia/phpwiki/newcodebase/FulltextStoplist.php?rev=1.1&content-type=text/vnd.viewcvs-markup but do not no how that list was made. - Patrick 06:15 Apr 22, 2003 (UTC)

Isn't this an article title up with which we should not put? DJ Clayworth 18:59, 31 Oct 2003 (UTC)

The current stop word list is the default list built in to MySQL version 4.0.20. I'm currently doing some work to update it, mainly adding new words based on the peculiarities of this site and handling languages other than English. For those unfamiliar with stop words, they are words which are so common that a search for them would produce a uselessly large set of results. For example, until I add it to the stop word list, a search for 'redirect' will return more than 350,000 results. Stop word list is what I'll be using as a base page for this topic. The list in MySQL is documented as being derived from the Cornell University Smart software (smart.11.0.tar.Z), which has a brief description. One of the MySQL employees also asked for the Fulltext index statistics for en Wikipedia, which contains a list of the most frequent 5,000 words in the index (which doesn't include the stop words). Jamesday 13:23, 26 Nov 2004 (UTC)

The MySQL 4.0.20 stop word list is the list which has previously been used. See Stop word list for the ongoing work to improve it. Jamesday 22:17, 28 Nov 2004 (UTC)

noone
"Noone" should be a valid search. It is a common mistake and is not a word. Guanaco 18:20, 12 Dec 2004 (UTC)

Delete
I don't see any point to keeping this page. — Gulliver ✉ 07:11, 5 March 2006 (UTC)

Why is this linked from the standard "search failed" page?
If this page is more than two years out of date, why is it still linked from the WP Special page you get when a search returns no results? ~ MD Otley (talk) 00:57, 24 March 2008 (UTC)


text:
The Sum of Us (play)

The Sum of Us is a 1990 play by David Stevens. It is the third play in his now completed A Currency Trilogy of which the first play is The Inn at the Beginning of the World. The second play is The Beast and the Beauty produced by the Old Mill Theatre, Perth, on 22 June 2012.

Plot
The plot revolves around the comfortable relationship between widower Harry and his gay son Jeff and their individual searches for the right mate. Harry unconditionally loves his rugby-playing son and even takes an active part in Jeff's search for Mr. Right. Harry reveals that his mother (Jeff's grandmother) was a lesbian, perhaps accounting for his accepting attitude toward Jeff. Jeff's new boyfriend, Greg, who is closeted from his own homophobic father, finds it difficult to relate to Harry's well-meaning matchmaking ways. Greg is ejected from his own home by his father when he discovers his son's sexuality. Harry, via a video dating service, finds a woman that he likes, a divorcee named Joyce, who may not be so understanding after spying a gay magazine in Harry and Jeff's house. Unfortunately, Harry suffers a massive stroke and is left unable to speak or walk. Jeff cares for him as best as he can, taking him to the park for an outing one day. Jeff and Greg meet up in the park and agree to try and rekindle their romance, while Jeff's father, although unable to speak, gives his overwhelming approval.

Production
The play, directed by Kevin Dowling, opened on October 16, 1990 at the Off-Broadway Cherry Lane Theatre, where it ran for 335 performances. Tony Goldwyn and Richard Venture (edit: it was Richard THOMSEN) headed the cast. The play won the Outer Critics Circle Award for the Outstanding Off-Broadway Play 1990–1991.

The first production in Australia was in 1992 by the Sydney Theatre Company at the Wharf Studio Theatre with Ron Graham and Peter Phelps. A new production is touring capital cities, regional and remote venues across Australia in 2011. Produced by Christine Harris and HIT Productions, the cast includes one of Australia's most well-known television, theatre and film actors John Jarratt, alongside Patrick Harvey, Glenn van Oosterom, and Nell Feeney. Directed by Green Room Awards winner Denis Moore.

Adaptation
A 1994 Australian film adaptation also titled The Sum of Us was directed by Dowling and Geoff Burton and starred Russell Crowe and Jack Thompson. The screen adaptation mimics the play's device of breaking the fourth wall with direct to camera conversational asides by both Harry and Jeff. Stevens' screenplay won awards from the Australian Film Institute and the Montreal World Film Festival, and the movie was named Best Film at the Cleveland International Film Festival.

title: The Sum of Us (play)


text:
Eliot Ness

Eliot Ness (April 19, 1903 – May 16, 1957) was an American Prohibition agent known for his efforts to bring down Al Capone while enforcing Prohibition in Chicago. He was leader of a team of law enforcement agents nicknamed The Untouchables, handpicked for their incorruptibility. The release of his memoir The Untouchables, months after his death, launched several screen portrayals establishing a posthumous fame for Ness as an incorruptible crime fighter.

Early life
Eliot Ness was born on April 19, 1903, in the Roseland neighborhood of Chicago, Illinois. He was the youngest of five children born to Peter Ness (1850–1931) and Emma King (1863–1937). His parents, both Norwegian immigrants, operated a bakery. Ness attended Christian Fenger High School in Chicago. He was educated at the University of Chicago, graduating in 1925 with a degree in political science and business administration, and was a member of Sigma Alpha Epsilon. He began his career as an investigator for the Retail Credit Company of Atlanta assigned to the Chicago territory, where he conducted background investigations for the purpose of credit information. In 1929, he returned to the university to take a graduate course in criminology taught by August Vollmer, a noted police reformer and chief of the Berkeley Police Department. Vollmer's ideas about professionalizing law enforcement would influence Ness throughout his career.

1926–1931
Ness's brother-in-law, Alexander Jamie, an agent of the Bureau of Investigation (which became the Federal Bureau of Investigation in 1935), influenced Ness to enter law enforcement. Ness joined the U.S. Treasury Department in 1926, working with the 1,000-strong Bureau of Prohibition in Chicago.

In March 1930, attorney Frank J. Loesch of the Chicago Crime Commission asked President Herbert Hoover to take down Al Capone. Agents of the Bureau of Internal Revenue, working under Elmer Irey and Special Agent Frank J. Wilson of the Intelligence Unit, were already investigating Capone and his associates for income tax evasion. In late 1930, Attorney General William D. Mitchell, seeking a faster end to the case, implemented a plan devised by President Hoover for sending a small team of Prohibition agents, working under a special United States attorney, to target the illegal breweries and supply routes of Capone while gathering evidence of conspiracy to violate the National Prohibition Act (informally known as the Volstead Act). U.S. attorney George E.Q. Johnson, the Chicago prosecutor directly in charge of both the Prohibition and income tax investigations of Capone, chose the 27-year-old Ness (now assigned to the Justice Department) to lead this small squad.

With corruption of Chicago's law enforcement agents endemic, Ness went through the records of all Prohibition agents to create a reliable team (initially of six, eventually growing to about ten) later known as "The Untouchables." Raids against illegal stills and breweries began in March 1931. Within six months, Ness's agents had destroyed bootlegging operations worth an estimated $500,000 (almost $9.9 million in 2022) and representing an additional $2 million ($39.5 million in 2022) in lost income for Capone; their raids would ultimately cost Capone in excess of $9 million ($178 million in 2022) in lost revenue. The main source of information for the raids was an extensive wiretapping operation.

In 1931, a member of Al Capone's gang promised Ness that he would receive $2,000 every week ($36,684.27 in 2022) if he ignored their bootlegging activities. Ness refused the bribe. Failed attempts by members of the Chicago Outfit to bribe or intimidate Ness and his agents inspired Charles Schwarz of the Chicago Daily News to begin calling them "untouchables". George Johnson adopted the nickname and promoted it to the press, establishing it as the squad's unofficial title.

The efforts of Ness and his team inflicted major financial damage on Capone's operations and led to his indictment on 5,000 violations of the Volstead Act in June 1931. Federal judge James H. Wilkerson prevented that indictment from coming to trial, instead pursuing the tax evasion case built by George Johnson and Frank Wilson. On October 17, 1931, Capone was convicted on three of 22 counts of tax evasion. He was sentenced to eleven years in prison and, following a failed appeal, began his sentence in 1932. On May 3, 1932, Ness was among the federal agents who took Capone from the Cook County Jail to Dearborn Station, where he boarded the Dixie Flyer to the Atlanta Federal Penitentiary—the only time the two men are known to have met in person.

1932–1957
In 1932, Ness was promoted to Chief Investigator of the Prohibition Bureau for Chicago. Following the end of Prohibition in 1933, he was assigned as an alcohol tax agent in the "Moonshine Mountains" of southern Ohio, Kentucky, and Tennessee, and in 1934 he was transferred to Cleveland, Ohio. In December 1935, Cleveland mayor Harold H. Burton hired Ness as the city's Safety Director, which put him in charge of both the police and fire departments. Ness soon began a reform program inspired by the ideas of August Vollmer, which focused on professionalizing and modernizing the police, stopping juvenile delinquency, and improving traffic safety. He declared war on the mob, and his primary targets included "Big" Angelo Lonardo, "Little" Angelo Scirrca, Moe Dalitz, John Angerola, George Angersola, and Charles Pollizi.

Ness was also Safety Director at the time of the murders known as the Cleveland Torso Murders, occurring in the Cleveland area from 1935 to 1938; though he had oversight of the police department, he was only peripherally involved in the investigation. Ness interrogated one of the prime suspects of the murders, Dr. Francis E. Sweeney, using a polygraph test. At one point in time, two bodies of the victims of the serial killer were placed within view of his office window.

In 1938, Ness and his wife Edna divorced. His otherwise successful career in Cleveland withered gradually. He especially fell out of favor after he had the city's large shantytowns evacuated and burned during the Cleveland Torso Murders. Cleveland critics targeted his divorce, his high-profile social drinking, and his conduct in a car accident one night when he was driving drunk. Although there were no victims in the accident, Ness, fearful that he might lose his job, tried to get the accident covered up. Later, his involvement in the accident was revealed by a local newspaper and calls for his resignation increased; however, Burton's successor as mayor, Frank Lausche, kept Ness on.

In 1939, Ness married illustrator Evaline Michelow. In 1942, the Nesses moved to Washington, D.C., where he worked for the federal government. He directed the battle against prostitution in communities surrounding military bases, where venereal disease was a serious medical issue. Later he made a number of forays into the corporate world, all of which failed owing to his lack of business acumen. In 1944, he left to become chairman of the Diebold Corporation, a security company based in Ohio.

After his second divorce and third marriage, he ran unsuccessfully for Mayor of Cleveland in 1947, after which he left Diebold in 1951. In the aftermath, Ness was forced into taking odd jobs to earn a living, including bookstore clerk and wholesaler of electronics parts and frozen hamburger patties. By 1956, he came to work for a startup company called Guaranty Paper Corporation, which claimed to have a new method of watermarking legal and official documents to prevent counterfeiting. Ness was offered the job because of his expertise in law enforcement and moved from Cleveland to Coudersport, Pennsylvania, where much of the investment capital for the company was located. Now drinking more heavily, Ness spent his free time in a local bar, telling stories of his law enforcement career. Guaranty Paper began to fall apart when it became clear that one of Ness's business partners had misrepresented the nature of their supposedly proprietary watermarking process, leaving Ness in serious financial jeopardy.

In later years, Ness struggled financially; he was nearly penniless at the time of his death, with his role in bringing down Al Capone having been largely forgotten.

Personal life
Ness was married to Edna Stahle (1900–1988) from 1929 to 1938, illustrator Evaline Michelow (1911–1986) from 1939 to 1945, and artist Elisabeth Andersen Seaver (1906–1977) from 1946 until his death in 1957. He also had an adopted son, Robert (1946–1976).

Death
Shortly after his approval of the final galleys for The Untouchables, on whose writing he and Oscar Fraley had been collaborating as a means, on Ness' part, of earning money in his later years, Ness collapsed and died of a heart attack at his home in Coudersport, Pennsylvania, on May 16, 1957. He was 54 years of age. His body was cremated, and his ashes were scattered in one of the small ponds on the grounds of Lake View Cemetery in Cleveland. An admirer later donated a plot near the pond and erected a cenotaph in his honor there.

Ness was survived by his widow, Elisabeth Andersen Seaver, and adopted son, Robert.

Archive
The Western Reserve Historical Society houses additional Ness papers, including a scrapbook (1928–1936), copies of newspaper clippings (1935–1950), a typewritten manuscript detailing Ness's career in Chicago, and miscellaneous papers, including a report on the Fidelity Check Corporation and Guaranty Paper, of which Ness was president.

Art, entertainment, and media
Numerous media works have been developed based on Eliot Ness's life and the legend surrounding his work in Chicago. The first of these resulted in Ness's last years in collaboration with Oscar Fraley in writing the book The Untouchables (1957), which was published after Ness's death and went on to sell 1.5 million copies. Although the historical veracity of this book has been questioned, later research suggests that it is broadly accurate. A 21-page manuscript that Ness wrote for the book is housed in the archives of the Western Reserve Historical Society in Cleveland, Ohio.

The book was adapted in multiple media and inspired many additional works. The best-known adaptations include the 1959 TV series The Untouchables, which starred Robert Stack as Ness and was narrated by Walter Winchell, and the 1987 film The Untouchables, directed by Brian De Palma, which starred Kevin Costner as Ness, Sean Connery and Robert De Niro as Al Capone. These two fictionalized portrayals, more than actual history, have inspired numerous novels; a TV-movie, The Return of Eliot Ness, in which Stack returned to the role; a second, short-lived 1993 TV series titled The Untouchables, which starred Tom Amandes as Ness and William Forsythe as Capone; stage plays such as Peter Ullian's In the Shadow of the Terminal Tower; and comic books such as Torso. Ness was portrayed by actor Jim True-Frost in the fifth-season episode "The Good Listener" of the HBO television series Boardwalk Empire.

Max Allan Collins used Ness as the "police contact/best friend" character in his series of historical private eye novels featuring Chicago detective Nate Heller. Later he spun Ness off into his own series, set during his tenure as Cleveland's Public Safety Director. The first book, The Dark City (1987), depicted Ness's getting hired and undertaking a cleanup of the graft-ridden police force; the second, Butcher's Dozen (1988), his pursuit of the serial killer known as the Mad Butcher of Kingsbury Run. Bullet Proof (1989) pitted Ness against labor racketeers intent on taking over Cleveland's food service industry. Ness is mentioned in many hip hop and rap tracks ("California Love", for example). Murder by the Numbers (1993) depicted Ness's investigation of the numbers racket in Cleveland. All of these novels, while fictionalized, were closely based on actual cases investigated by Ness and the Cleveland Police. Collins also wrote a one-man stage play, Eliot Ness – An Untouchable Life, which was nominated for an Edgar Award. Collins wrote Ness into his graphic novel Road to Perdition.

In 2018, Collins collaborated with historian A. Brad Schwartz on a nonfiction dual biography of Ness and Capone entitled Scarface and the Untouchable: Al Capone, Eliot Ness, and the Battle for Chicago. Collins and Schwartz are currently writing a second volume about Ness's years in Cleveland, entitled The Untouchable and the Butcher.

In The Young Indiana Jones Chronicles, Frederick Weller portrayed a young Elliot Ness in the eleventh episode The Mystery of the Blues. In the episode, he is portrayed as the roommate of Indiana Jones at the University of Chicago.

In the video game called The Untouchables was released in 1989 by Ocean Software on ZX Spectrum, Amstrad CPC, Commodore 64, MSX, Atari ST, Amiga, DOS, NES, and SNES.

Beer
Cleveland-based Great Lakes Brewing Company, which claims several connections to Ness (including the brewery owners' mother having worked as his stenographer), named an amber lager "Eliot Ness" and included several subtle nods to his career in the beer description and label art.

Proposed building naming
On January 10, 2014, Illinois U.S. Senators Dick Durbin and Mark Kirk and Ohio Senator Sherrod Brown proposed naming the headquarters of the Bureau of Alcohol, Tobacco, Firearms and Explosives in Washington, D.C., after Ness. If approved, it would have been called the Eliot Ness ATF Building. Brown said in a statement: "Eliot Ness is perhaps best known as the man who helped to bring Al Capone to justice. But Eliot Ness was more than just a Chicago U.S. prohibition agent. He fought for law and justice in Ohio, and fought for peace and freedom in World War II. He was a public servant and an American hero who deserves to be remembered."

Chicago Aldermen Edward M. Burke (14th Ward) and James Balcer (11th Ward) introduced a resolution in the Chicago City Council to oppose the renaming. In a news release, Burke said: "Eliot Ness had a checkered career after leaving the federal government. I simply do not think his image matches the actual reality of his legacy."

The authors of two separate Ness biographies later disputed the accuracy of Burke's claims, suggesting he mischaracterized Ness's career. "If Hollywood has given Eliot Ness too much credit for getting Capone," Max Allan Collins wrote in an article for HuffPost, "he has received too little credit anywhere else for helping professionalize law enforcement in the mid-20th Century."

Although the Senate resolution was never adopted, the main atrium in the ATF headquarters building was later renamed for Eliot Ness and features a historical exhibit about the Untouchables.

Festival and museum
Coudersport, Pennsylvania, the town where Ness spent his final months and died, has held an annual "Eliot Ness Festival" every third weekend in July since 2018. Past events have included a public reunion of people descended from the original Untouchables, a dramatization of Al Capone's trial, film screenings, author talks, and antique car shows.

In 2019, an "Eliot Ness Museum" inspired by the annual festival opened in downtown Coudersport, featuring several antique cars and exhibits describing Ness's life and career.

title: Eliot Ness


text:
Jingo (novel)

Jingo is a fantasy novel by British writer Terry Pratchett, the 21st book in his Discworld series. It was published in 1997.

Plot
At the opening of the novel, the island of Leshp, which had been submerged under the Circle Sea for centuries, rises to the surface. Its position, exactly halfway between Ankh-Morpork and Al Khali (the capital of Klatch), makes the island a powerful strategical point for whoever lays claim to it, which both cities do.

In Ankh-Morpork, a Klatchian Prince named Khufurah is parading through Ankh-Morpork, where he will be presented with a Degree in Sweet Fanny Adams (Doctorum Adamus cum Flabello Dulci), but is wounded in an assassination attempt. Sir Samuel Vimes, Commander of the Ankh-Morpork City Watch, originally suspects both a Klatchian named 71-Hour Ahmed and a senior Morporkian peer, Lord Rust, of involvement.

The attempted assassination breaks off relations between Ankh-Morpork and Klatch as Prince Khufurah's brother, Prince Cadram, effectively declares war on the city of Ankh-Morpork. At this point, Havelock Vetinari, Patrician of Ankh-Morpork, resigns—apparently of his own free will—and Lord Rust takes command of the city. Vetinari refused to become involved in the war with Klatch since Ankh-Morpork does not have an army, but Rust declares martial law and orders the city's noble families to revive their old private regiments.

Vimes, refusing to follow Rust, stands down as Commander of the Watch. Captain Carrot resigns as well, as do Sergeant Colon, Sergeant Detritus and Corporal Angua. The idea of putting the watch under the command of Corporal Nobbs is rejected by the ruling Council of Guild leaders and the Watch is disbanded. Vimes then recruits the Watch into his own private army regiment, reasoning that, as an official noble, he is entitled to do so by law and by Lord Rust's command, with the group remaining independent as knights legally fall under command of the king or his duly appointed representatives, neither of which exist in Ankh-Morpork.

Angua, following 71-Hour Ahmed, is captured by the Klatchians and taken to Klatch. Carrot, rather than rush off to save her, reports back to Vimes, who gets his private army to head for Klatch. Meanwhile, Nobby and Sergeant Colon have been recruited by Vetinari and his pet inventor, Leonard of Quirm, on a secret mission of their own, unknown to Vimes.

Vetinari, Leonard of Quirm, Colon, and Nobby end up in Leonard's "Going-Under-the-Water-Safely Device" and discover that Leshp is actually floating on top of a huge bubble of gas, and that the gas is escaping from said bubble, meaning that Leshp will, ultimately, sink back under the sea again.

Vimes catches up with 71-hour Ahmed and has, by this time, figured out that Ahmed is a fellow policeman. Ahmed tells Vimes that Prince Cadram was responsible for the assassination attempt on Prince Khufurah. Ahmed and his band of Klatchian D'regs and Vimes' army head towards Gebra, in Klatch, where the war is due to start.

To help blend in, Vetinari, Nobby and Fred Colon get hold of some Klatchian clothing, though Nobby ends up wearing the costume of a dancing girl and gets in touch with his feminine side. The three also head to Gebra, where they discover that Carrot has convinced the two armies to get together and play a game of football, Vimes is preparing to arrest both Klatchian Prince Cadram and Lord Rust for various breaches of the peace (such as being prepared for war), and 71-hour Ahmed is supporting him. Vetinari prevents an international incident by ostensibly declaring the surrender of Ankh-Morpork and offering war reparations, to be ratified on Leshp in one week.

Vetinari is returned to Ankh-Morpork, under arrest and in disgrace, but as Leshp has vanished back under the sea again, the treaty was to be signed in a non-existent territory and thus the charge of treason is invalid. Seeing he has been tricked, and with the people and generals turning against him, Prince Cadram flees, with 71-hour Ahmed in pursuit. His brother Khufurah recovers and assumes control of Klatch. Vimes is informed that Vetinari has been "reminded" that the old rank of Commander was the same as the old rank of Duke. He objects, claiming that only a King can make a Duke, but then realises that Carrot was speaking to Vetinari. Since Carrot is, of course, very much not the King of Ankh-Morpork his reminding of Vetinari is all that is required for Vimes to get his new position and rank. However, Vimes later attempts to get out of his own investiture ceremony half-way through by giving chase to an apprentice thief.

Vimes "accidentally" loses his "dis-organiser" (given to him by his wife) which kept giving him incorrect information. It is explained that, had Vimes reacted slightly differently in the beginning—staying in Ankh-Morpork rather than attempting to follow Ahmed and rescue Angua—the Morporkian-Klatchian war would have resulted in the invasion of Ankh-Morpork and the deaths of the entire Watch.

Characters

 * 71-hour Ahmed
 * Angua
 * Prince Cadram
 * Fred Colon
 * Detritus
 * Lt Hornett
 * Carrot Ironfoundersson
 * Cheery Littlebottom
 * Nobby Nobbs
 * Leonard of Quirm
 * Lord Rust
 * Reg Shoe
 * Havelock Vetinari
 * Samuel Vimes

Reception
In Interzone, John Clute described Jingo as fitting "seamlessly" into the Discworld, commenting that it does not "dishonour its predecessors in the series" and "is in fact better than most of them". Clute also compared Pratchett's writing to that of P. G. Wodehouse, and noted the presence of "totemic moments", and of several scenes which he felt to be "homilies".

Escape Pod stated that a significant portion of the plot is "Vimes subverting the status quo in ways that shouldn't work, but somehow do anyway". The SF Site ranked it "above Feet of Clay but not quite as good as Guards! Guards!", considering that "The story stumbles a bit, especially once the action moves to Klatch, and there are few nitpicky things here and there", but concluding that it is nonetheless "a fine addition" to the Discworld.

title: Jingo (novel)