text:
Talk:XMLHttpRequest

For older discussion on this article dating from 2005-2008, please see Talk:XMLHttpRequest/2005-2008.

setRequestHeader
Can anyone provide a source for this statement: If the Content-Type request header was not added through setRequestHeader yet, it should automatically be added by a conforming user agent as "application/xml;charset=charset," where charset is the encoding used to encode the document.

It appears that it is not possible to set the charset of the Request Header. It is always set to UTF-8, regardless of the document encoding. —Preceding unsigned comment added by Nepherim (talk • contribs) 18:32, 13 June 2010 (UTC)

Known bugs
Can anyone provide any reference to show that the IE cache bug descirbed in the 'known bugs' is correct? I have never encountered this problem. --Sleepyhead 10:31, 20 August 2005 (UTC)

 * Neither have I, there is probably no bug. Taka 14:42, 29 October 2005 (UTC)

I remember having problems with opera caching get requests using this. I appeneded a unixtimestamp to avoid it though.

 * I've seen this problem with IE6. I think it only happens when you send requests from more than one Javascript function. For example, I'm using Ajax to update dropdowns. Setting one queries the database for values for the second. Setting the second dropdown queries the database for values for the third dropdown. But what might be helpful here is a better description of what non-idempotent operations are. DRogers 23:16, 4 October 2006 (UTC)

I experienced a problem where IE would cache the previous XML response while Firefox would always refresh. In the end simply getting the servlet that returned the XML to add the HTTP header 'Expires: -1' seemed to fix the problem - it now works fine with both browsers. --Stuartallen1972 00:53, 31 October 2007 (UTC)

 * I have personally observed this bug over many years. I personally verified that it remains in IE7 in February of 2008. DRogers is incorrect, it happens even when you have just one js function. I tried every combination of request header on the client and response header on the server that I could find documetation for and IE still returned the stale page from the cache instead of the fresh page from the server.

 * I find that most documents fall into one of three categories. A) They never change and the default IE behavior does not hurt and does conserve network capacity so it is left in place. B) The pages change, but data that is out of date does not hurt any one, so the default behavior is left in place to gain the benefits of caching. C) The data does change and stale data has consequences, so the developer, in frustration adds the timestamp to the URL, thereby not only defeating the cache but polluting it with many cached pages that will never be referred to, one for each refresh of the URL. The wasted time, network capacity and local storage are considered a small penalty to pay in exchange for eliminating the possibility of stale data.  When the response is tiny, then as a practical matter, this may be true, but after years of serving data that fell in one of those three categories, I encountered for the first time a situation that falls in a 4th category. A response that was critical and large.  The typical response of adding a timestamp to the URL was no longer acceptable.  My users were going to pay and pay and pay for my sloppiness. Each time they visited or refreshed the page, they were going to reload a large document that in turn had the potential to fill their cache space with documents that would never be referenced.  I was finally ready to invest the time to solve the issue instead of bypassing it as I had done for years. As I researched it, I did find it reported in many places on the web, and I did see a few half baked approaches to solving it, and at least one case where a solution was described but not presented .  I pretty much had my solution coded and working before I arrived at this page, where I saw it presented in the most elegant form that I had yet seen.

 * The discussion of what does or does not belong in Wikipedia is frustrating. The answer is not black and white.  I can think of all kinds of code that I would not want to see posted because it would obscure the "encyclopedic" content of the page. In this case, the bug has been around for ever, the solution is simple and elegant; it works perfectly for all 4 categories of data that I mentioned above. It provides all of the benefits of caching and all of the benefits of getting a fresh copy each time and never polluting the user’s cache. Finally, allowing such a code snippet on this page provides the biggest benefit of all which is being vetted by thousands of the most dedicated people in the world, you (and me).  That is not possible if we send people elsewhere to find the code or algorithm.  This brings me to this point.

 * Why in the code sample do we send null in the first send and an empty string in the second? I don't think there is functionally difference, you’re going to get to newlines in a row in the data stream sent to the host in either case, but it gives the impression that there is a difference and that the difference is significant which makes an observant reader take off on a wild goose chase. I propose that null be used in both instances, to avoid confusion.

 * In conclusion, I think that the code samples definitely belong on the page in this case. It is too important; everyone that uses XHR needs to know about the issue and the elegant solution. And everyone will benefit by having it vetted and improved upon and improved upon so that it is the cleanest and most elegant that it can be. -- Gary D. —Preceding unsigned comment added by 97.88.245.62 (talk) 17:17, 1 March 2009 (UTC)

Please keep short IE 5-6 compatibility code
The article correctly states IE had XHR in versions prior to 7. However, I notice someone has been removing the fact that versions before 7.0 cannot instantiate the now-standard XMLHttpRequest class without workarounds, because the original Microsoft XMLHTTP was not a class of its own, but an ActiveXObject. None of the examples on the page work in IE 5.x-6.x without code somewhat like this, and the info on the page is misleading without it, so please discuss here before removing it again: 74.192.58.22 (talk) 16:17, 27 August 2008 (UTC)

 * I don't think this listing adds encyclopedic value, and removed it. Wikipedia is not a how-to, and should keep the discussion of backwards compatibility to a high level, appropriate for the context. Any readers interested in actual implementation details can find them in the cited sources and external links. --Piet Delport (talk) 14:27, 6 January 2011 (UTC)

Move API ( property function method in other article ?
methods and properties have no reason to be in a wikipedia article. Resume it to help people discover what it can do ll be more intructive. as a developper find this chapter usefull but not for non programmer. perhaps specific code could be keep ? —Preceding unsigned comment added by 92.131.191.80 (talk) 17:06, 3 September 2008 (UTC)

 * Yes, many have heard the term xmlhttp and come here to discover what it is. Many others (like me) come here to find out how to get xmlhttp to do what it does. You (rightly, imo) object to the immediate plunge into technical content in the opening sentences. So let us prepare a short introductory paragraph for the incognoscenti that will/should answer most of their questions. Example: a high-level understanding of xmlhttp is a small but essential part of understanding web 2.0. So let's tell the lay visitor that in a few sentences and move on to the very-much-needed technical discussion. Like the lead paragraph in a newspaper story: what is it; and why is it?   — Preceding unsigned comment added by Pete142 (talk • contribs) 11:15, 10 January 2011 (UTC)

 * sigh* I came here as a programmer to look at the wonderful example and its gone. Gone in the name of arbitrary order for order's sake, it looks like. It wasn't hurting anything. —Preceding unsigned comment added by 68.127.178.106 (talk) 06:02, 2 September 2009 (UTC)
 * Yeah, we seem to have a 'dumbing-down' brigade who hate code examples in articles - it's happened on XML, SVG, CSS etc etc. Apparently we need more history and media comment. Yet they don't seem to mind almost impenetrable mathematical articles like Negligible function. Media studies is the future (but hopefully, some of us will still remember how the software works) :o) --Nigelj (talk) 16:35, 2 September 2009 (UTC)

 * Well, I guess wikipedia isn't interested in being a handy programmer reference anymore. I'm not convinced this makes wikipedia better, but it's not a huge deal either way. 66.68.113.5 (talk) 05:37, 22 September 2009 (UTC)

Wikipedia links to handy programmer references: it isn't one itself. --Piet Delport (talk) 14:33, 6 January 2011 (UTC)

 * Well, Piet, many believe that Wikipedia has become the resource it is because people have contributed material that interests them, thinking it might interest others as well. How did you conclude that this belief is in error?

I, too, came here looking for xmlhttp info. If there is code too, well, bravo! So much the better! It means I can save thirty minutes. So please: don't remove any code. — Preceding unsigned comment added by Pete142 (talk • contribs) 10:44, 10 January 2011 (UTC)

What's XML-RPC got to do with it ?
This paragraph seems a bit out of place:

 * "This type of AJAX architecture should not be confused with (XDR) XDomainRequest which is a lightweight form of the XMLHttpRequest design by Microsoft which doesn't utilize XML-RPC."

because XMLHttpRequest doesn't use XML-RPC either, and it's not mentioned anywhere else in the article or in the citation for that Microsoft API. Perhaps I'm missing something though, so leaving it for someone who knows more about this stuff than me. --Qef (talk) 12:08, 10 July 2009 (UTC)

 * Correct. XDomainRequest and XMLHttpRequest are for sending requests and receiving responses through protocols (for XMLHttpRequest, specifically the HTTP and HTTPS protocols as defined by W3C). XML-RPC is a way to structure requests and responses using XML for creating language-independent communication between applications through protocols. XMLHttpRequest does not even require XML. The XML in "XMLHttpRequest" is not referring to the request Content-Type or the response Content-Type, only the fact that if the response is an Internet media type for XML, it should be parsed into a DOM Document object automatically. And even if it was an XML response, I don't believe (and could ever imagine) any user agents implemented a version of XMLHttpRequest that searches for and handles XML-RPC in the response automatically, too.

 * To clarify what XDomainRequest really is, it is a wrapper/object in IE8 which implements the interfaces of the XMLHttpRequest object with additional support for cross-domain requests and progress events. Similar features are planned for the XMLHttpRequest object itself in the level 2 specification, which is still a working draft, as is the level 1 specification still...

 * Good spot on that, Qef. I'd like to know what the person that wrote that meant by it/was referring to. --Quilokos (talk) 23:28, 10 July 2009 (UTC)

Referencitis
First time I am reading the article and I notice that the "HTTP request" section has been tagged as having no reference. Looking through the history, the revision this has been done is "10:38, 1 October 2010 Mabdul". Although I can understand that two citations aren't much for that amount of text, a better thing to do would have been to look for references where you thought they would have been useful. I've been observing a tendency to flag things instead of contributing. If people have enough knowledge to flag, I'm expecting that they also have enough knowledge to correct things too. Otherwise, what I've learnt today on this article wouldn't have been available to me. There should be a middle ground between flagging and leaving, and contributing. — Preceding unsigned comment added by Amenel (talk • contribs)
 * I can understand you're opinion and your concerns about only-tagging articles. For my defense I have to say that I'm working on really many articles simultaneous and my watchlist has since a few weeks over 600 pages! (ok, some may redirects I created) In many articles I'm constantly adding more references or expanding these articles. I have not the time to expand this article also. mabdul 14:04, 25 January 2011 (UTC)

The onreadystatechange event listener
This section contains flawed example code. It would be better to correct the code.

Specifically:

1) the code example shows the send method called before the callback event is defined; and

2) the text following the code discusses the effect of calling the send method before the open method (reversing the first two lines)

It would surely be better to include good code and, if there are inconsistencies between browsers when such code executes, discuss those inconsistencies, rather than the problems that might be caused by poorly written code.

Showing bad coding examples and then discussing what's wrong with them may be appropriate for an article about good and bad coding practices, but it's not appropriate here.

--DMcMPO11AAUK/Talk/Contribs 19:06, 15 April 2011 (UTC)

Neither limited to XML nor HTTP
The article portrays XMLHttpRequest as supporting http and https and XML and plain text. That's the way XMLHttpRequest was originally, but since then, it has evolved to a more generic scriptable URL fetch mechanism.

These days, at least the development versions of all major browsers support URL schemes beyond http: and https:. In particular, blob: URLs are supported, see http://dev.w3.org/2006/webapi/FileAPI/ for spec.

Response types beyond XML and plain text are supported. These days, HTML, byte buffer and JSON responses are supported, too. See: https://developer.mozilla.org/En/HTML_in_XMLHttpRequest http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html https://bugzilla.mozilla.org/show_bug.cgi?id=707142 http://www.html5rocks.com/en/tutorials/file/xhr2/

I'm not making edits to the article myself, since my edits would probably get reverted as violating some Wikipedia policy against primary sources as I have implemented some of these features for Firefox/Gecko. Hsivonen (talk) 11:32, 5 February 2012 (UTC)

Maintenance and rating of JavaScript articles
Concerning editing and maintaining JavaScript-related articles...

Collaboration...
If you are interested in collaborating on JavaScript articles or would like to see where you could help, stop by WikiProject JavaScript and feel free to add your name to the participants list. Both editors and programmers are welcome.

Where to list JavaScript articles
We've found over 300 JavaScript-related articles so far. If you come across any others, please add them to that list.

Aren't this kind of stuff should be made by special page Category:JavaScript page?82.142.169.244 (talk) 14:00, 4 August 2017 (UTC)

User scripts
The WikiProject is also taking on the organization of the Wikipedia community's user script support pages. If you are interested in helping to organize information on the user scripts (or are curious about what we are up to), let us know!

If you have need for a user script that does not yet exist, or you have a cool idea for a user script or gadget, you can post it at User scripts/Requests. And if you are a JavaScript programmer, that's a great place to find tasks if you are bored.

How to report JavaScript articles in need of attention
If you come across a JavaScript article desperately in need of editor attention, and it's beyond your ability to handle, you can add it to our list of JavaScript-related articles that need attention.

Rating JavaScript articles
At the top of the talk page of most every JavaScript-related article is a WikiProject JavaScript template where you can record the quality class and importance of the article. Doing so will help the community track the stage of completion and watch the highest priority articles more closely.

Thank you. The Transhumanist 01:15, 12 April 2017 (UTC)

Feature detection outdated
if (window.XMLHttpRequest) ? Really? This is 2020, all major browsers support this feature without polyfills, and very few APIs bother checking. — Preceding unsigned comment added by 172.56.42.63 (talk) 02:18, 27 December 2020 (UTC)

Ajax?
"Particularly, retrieval of data from XHR for the purpose of continually modifying a loaded web page is the underlying concept of Ajax design."
 * The meaning and significance of that statement in the context is entirely non-obvious. Some overhaul (rewriting) can help. Regards, ... PeterEasthope (talk) 19:00, 20 January 2023 (UTC)

XHR is an API
This really isn't open to dispute. First line of the latest standard: "The XMLHttpRequest object is an API". The object implements an interface. One programs applications using that object that implements that interface. The standard specifies the required behavior of the interface, which in browser JavaScript runtimes is bound to objects created by calls to a constructor. There is no requirement that the objects are instances of a class in JavaScript or any other language. 2601:642:4600:D3B0:9111:FF68:B849:3D9B (talk) 21:00, 8 April 2024 (UTC)

I will add that the description of the methods appears to be written by someone who has never programmed an HTTP request in their life. "The HTTP request method may be GET for typical quantities of data." Nonsense. One does not choose between GET and POST based on the quantity of information sent, but why it is sent: to retrieve a resource, or to create/alter one. "If the request method of POST is invoked, then the web server expects the form data to be read from the standard input stream." That has nothing to do with XMLHttpRequest, and furthermore it isn't true. The data sent in a POST request isn't necessarily "form data", and the server can take it in any manner whatsoever. Taking it on standard input is a particular convention of CGI, a nearly obsolete technology. 2601:642:4600:D3B0:9111:FF68:B849:3D9B (talk) 22:57, 8 April 2024 (UTC)
 * * Regarding I will add that the description of the methods appears to be written by someone who has never programmed an HTTP request in their life.: Please refrain from personal attacks. Timhowardriley (talk) 07:27, 9 April 2024 (UTC)
 * * Regarding Nonsense: If you want to drill down on anything specific, then address it in a talk section. Be prepared to support your assertions with reliable sources. Timhowardriley (talk) 07:27, 9 April 2024 (UTC)

 * I will not refrain from criticizing the inclusion of wanton misinformation in the article. From HTTP 1.1: "The GET method means retrieve whatever information … is identified by the Request-URI." "POST is designed to allow … annotation of existing resources; posting a message …; providing a block of data … to a data-handling process; extending a database through an append operation." For a deeper discussion see Roy Fielding's dissertation on REST. 2601:642:4600:D3B0:9111:FF68:B849:3D9B (talk) 13:54, 9 April 2024 (UTC)

 * Would you like to explain what you suppose this code would do:  2601:642:4600:D3B0:9111:FF68:B849:3D9B (talk) 14:13, 9 April 2024 (UTC)
 * * Regarding what the HTTP 1.1: says: The HTTP 1.1 is confusing. What Michael Mahemoff wrote in "Ajax Design Patterns" (published by O'Reilly) simplified the distinction. Timhowardriley (talk) 14:44, 9 April 2024 (UTC)
 * * Regarding request.open( "DELETE", null );: Please provide some context. Timhowardriley (talk) 14:44, 9 April 2024 (UTC)
 * * Regarding I will not refrain from criticizing the inclusion of wanton misinformation in the article.: Please keep the discussion cordial. Timhowardriley (talk) 14:44, 9 April 2024 (UTC)
 * * Regarding For a deeper discussion see Roy Fielding's dissertation on REST.: If material in this dissertation is germane to the discussion, then quote from it to support an assertion. Timhowardriley (talk) 14:44, 9 April 2024 (UTC)

 * HTTP 1.1 is a technical standard, and it is definitive. If it's "confusing", the burden is on the reader to demonstrate that. The "context" is that you added that code to the article a year ago. 2601:642:4600:D3B0:9111:FF68:B849:3D9B (talk) 14:50, 9 April 2024 (UTC)

 * Ruby on Rails was a significant influence in the adoption of REST-based server APIs. From Ruby on Rails for Microsoft Developers by Antonio Cangiano (credentials): "The Golden Rule of web development is that any request that retrieves information should be a GET request, and any request that affects the data stored on the server should use the POST HTTP method." (nb: Rails was introduced when support for PUT and DELETE was inconsistent, and it allows them to be tunneled through POST requests.) "This rule is constantly violated, and it's not uncommon to see publicly accessible links that issue GET requests and have the ability to delete or modify data…. You should avoid this at all costs." Indeed it is often violated, which is why I used to ask people about the difference in job interviews, and why I don't have much tolerance for text here that propagates such error. 2601:642:4600:D3B0:9111:FF68:B849:3D9B (talk) 15:32, 9 April 2024 (UTC)
 * What sentence in the article are you refuting? What should the sentence be instead? What source are you basing this change on? Timhowardriley (talk) 15:55, 9 April 2024 (UTC)

 * The same sentence that I quoted above! I don't see a reason that the article should say anything about choosing between GET and POST because XHR sends either just as well and this isn't an article on how to implement a RESTful service. 2601:642:4600:D3B0:9111:FF68:B849:3D9B (talk) 16:02, 9 April 2024 (UTC)

title: Talk:XMLHttpRequest


text:
Wikipedia:Articles for deletion/Deaths in August 2005

Deaths in August 2005
There seems to be no reason to have this separate article which while it does not exactly duplicate Deaths in 2005 but has very much similar content. I propose that this debate also applies to articles in the series such as Deaths in July 2005, Deaths in June 2005, ... AYArktos 10:31, 20 August 2005 (UTC) Instead of deletion I have redirected for time being similar to the edit of 9 July to Deaths in July 2005 which was only activated as an article to archive the deabte from Deaths in 2005 after the month had ended. Once August 2005 has ended the two pages can be merged. I have removed reference to this page from the VfD log - this page should probably be removed--AYArktos 10:54, 20 August 2005 (UTC)

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


text:
Photograph (Nickelback song)

"Photograph" is a song by Canadian rock band Nickelback. It was released on August 8, 2005, as the first single from their fifth studio album, All the Right Reasons. The song reached the top ten in Australia, Austria, Belgium, the Netherlands, New Zealand, and the United States.

Background
The song is mostly autobiographical. Singer Chad Kroeger said, "It's just nostalgia, growing up in a small town, and you can't go back to your childhood. Saying goodbye to friends that you've drifted away from, where you grew up, where you went to school, who you hung out with and the dumb stuff you used to do as a kid, the first love — all of those things. Everyone has one or two of those memories that they are fond of, so this song is really just the bridge for all that."

Kroeger said the photograph he holds up in the music video of himself and his friend Joey Moi with a champagne chiller on Joey's head is the same one he referred to in the lyrics. He also admitted he had broken into his high school to steal money from the office safe eleven times, but "half a dozen" flowed better for the lyrics.

Chart performance
The single became the band's third top ten hit in the United States, peaking at number two on the Billboard Hot 100 chart. "Photograph" has sold over 1.4 million digital downloads in the U.S., according to Nielsen SoundScan, though it is certified double platinum by the Recording Industry Association of America. "Photograph", was the first of three top ten hits from All the Right Reasons in New Zealand, peaking at number four.

The song also topped the Billboard Mainstream Rock Tracks and Pop 100 charts. The single was also a huge success on the Canadian charts, peaking at number-one and staying there for seven weeks.

In 2008, the single was once again showing on future single release lists in the UK. The single was re-released on June 23, 2008 to capitalise on the success of "Rockstar". "Photograph" was added to the C-list at BBC Radio 1 on May 21, 2008, climbing to the B-list the following week, and then to the A-List. It was also added to the BBC Radio 2 C-list. "Photograph" originally peaked at number 29 upon its first release, three years earlier. The song re-entered the UK Singles Chart at number 52 on June 10, 2008, climbed to number 29 a week later and reached a peak of number 18, two weeks after the physical release, out peaking the original release of the song.

Music video
The music video was directed by Nigel Dick and was filmed in Hanna, Alberta, Canada, the band's hometown. It begins with Chad Kroeger, the video's protagonist, walking along a lonely, sparsely populated street, holding up a photograph of himself and Nickelback's producer, Joey Moi (who is referred to in the line "And what the hell is on Joey's head?"). As the song progresses to the line "And this is where I grew up," he walks to a rusty mailbox, addressed as number 29025. As he speaks of sneaking out, the camera does not show the house itself but does show a view from the inside looking out at him, possibly suggesting someone else lives there now. He continues walking and comes to an older building marked as "Hanna High School" on the front (now a vacant field, the building is no longer there) announcing, "And this is where I went to school." He and his three other band members enter the gym with their gear and put on a seemingly impromptu concert alone. During the chorus, two band members go to an old junkyard and reminisce about a field where the rest of the band and their girlfriends are partying. Another experiences a similar event near an abandoned train yard, seeing his old girlfriend (most likely Kim, who was "the first girl I kissed") run near the tracks and kiss his younger self. The Hanna Roundhouse is shown. The camera then switches to flashbacks of various people ("I miss that town, I miss the faces") As the video ends, the flashback people get in their cars to go home as the band finishes the song.

One particular shot from the video, with Kroeger holding up a picture frame at the lyric "Look at this photograph", became an Internet meme, with users replacing the contents of the frame with other pictures. At the time of the song's release, the meme has been part of the general negative attitudes towards the band, and as attitudes towards the band shifted towards more favorable appreciation, the meme was still used for humorous purposes.

Use by Donald Trump
In early October 2019, United States President Donald Trump used a portion of the music video and song within a video posted on his Twitter account; it had the opening four words of the song in all capital letters as the caption for the tweet as used in the Internet meme taken from the video. The video was about former Vice President (and, later, President of the United States) Joe Biden and his son Hunter. The photo shows them on a golf course with Hunter's business partner, Devon Archer and raises questions about the precise nature of Archer and Hunter's past relations with Burisma in Ukraine, while also taking a shot at the elder Biden's appearance with the lyrics "What the hell is on Joey's head?".

The video containing the music video and four words of the song was subsequently removed from Twitter with the following message substituted in place of the video: "This media has been disabled in response to a report by the copyright owner." This entire series of actions, the posting of the video and its removal, was met with a significant rise in digital on-demand streaming of the song and music video as well as digital download sales of the song compared to streamings and downloads on the days before the tweet.

Google Photos
The band created a parody of the song for a Google Photos advertisement released in December 2020, with the lyrics making fun of Kroeger's own photographic history, including his noodle-like hair.

Track listings
CD single
 * 1) "Photograph" [album version] – 4:21
 * 2) "Photograph" [edit] – 3:55
 * 3) "We Will Rock You" – 2:01
 * 4) "Photograph" [video]

2008 CD single (UK re-release)
 * 1) "Photograph" [radio mix] – 3:49
 * 2) "We Will Rock You" – 4:29

title: Photograph (Nickelback song)


text:
Rear naked choke

The rear naked choke (RNC) is a chokehold in martial arts applied from an opponent's back. The word naked in this context suggests that, unlike other strangulation techniques found in jujutsu/judo, this hold does not require the use of a keikogi ("gi") or training uniform.

The choke has two variations: in one version, the attacker's arm encircles the opponent's neck and then grabs their own biceps on the other arm (see below for details); in the second version, the attacker clasps their hands together instead after encircling the opponent's neck. Recent studies have shown that the rear-naked choke takes an average of 8.9 seconds to render an opponent unconscious regardless of the grip that is used.

"Figure four" or "short" variation
This variant is considered to be a "blood choke" because it restricts blood flow to the brain via the carotid arteries. When applied correctly, it can cause temporary unconsciousness in a few seconds. The following is a description of this technique using the right arm:

 * 1) The attacker's right arm encircles the opponent's neck, with the opponent's trachea at the crook of the elbow.
 * 2) The attacker's right hand then grasps their own upper left arm [biceps].
 * 3) The left hand is placed behind (or occasionally on top of) the opponent's head. A more effective form of the choke can be applied by placing the palm of the left hand against the attacker's own shoulder rather than behind the opponent's head. This greatly reduces the escape possibilities.
 * 4) The elbows are then brought together such that lateral pressure, from the biceps and radius bone, is applied to the neck on both sides.

When applied properly, unconsciousness occurs in less than 10 seconds and recovery from the choke is just as quick.

"Body lock" or "hooks" variation
The placement of the legs usually falls into two categories. The first is a body lock. The attacker places one of their legs across the stomach or lower chest of the victim. They then place their other leg over their own shin, creating a figure-four with their legs. This allows them to limit movement and stay close to the back of their victim. This technique was used by Anderson Silva against Dan Henderson and by Jim Miller against Melvin Guillard. The other common technique is known as using "hooks". In this version the attacker places their legs inside of the victim's legs. They then move their legs out, placing their shin behind the victim's knees, essentially using their shins and feet as hooks to control the victim's legs. This variation leaves the attacker open to the possibility of leglocks from their opponent, as they are attacking the choke.

"Clasping hands" variation
This variation (also known as Palm to Palm) has the supporting hand clasp the hand of the choking arm, allowing more pressure to be applied to the neck, but losing some of the control of the head. This alters the choke somewhat so that it is more likely to be applied as an airway-restricting choke or mixed blood and air choke, which results in more pain but a slower choke-out. As such, this technique is less frequently used at advanced levels in Judo. Nonetheless, it has seen some successful applications in mixed martial arts competition: for instance, it was used by Fedor Emelianenko, a heavyweight champion in PRIDE, to defeat Kazuyuki Fujita at the PRIDE 26 event in 2003. Fujita tapped out about five seconds after the choke was applied. He used it again to defeat former UFC Heavyweight Champion Tim Sylvia in 36 seconds. Sylvia tapped out immediately once the choke was sunk in and after the fight described it as being very painful. It was also used by Ultimate Fighting Championship fighter Matt Hughes to defeat Frank Trigg in their second fight which was adapted from a hand-on-biceps version of the rear naked choke. Anderson Silva also used the clasping hands variation when he defeated Dan Henderson in the UFC. Joe Lauzon used this choke in his fight against Melvin Guillard, initially using the standard version, then switching to a palm to palm.

Judo
In Judo, the rear naked choke is known as Hadaka-jime : "naked choke", one of the 36 constriction techniques of Kodokan Judo in the Shime-waza list.

Technique
The main characteristic of Hadaka-Jime when compared with other Judo chokes is that it does not require the use of the opponent's clothing, namely their gi lapel, to create the choking tourniquet. It digs the blade of the wrist into the carotid sinus similar to the hand clasp method and uses a lever motion helped by the underhand. It is faster to apply requiring less strength than the figure four/mixed-martial arts version but is more difficult to learn. It is not an air choke but a carotid choke created entirely by the attacker's arms.

Similar non-judo techniques
Hadaka Jime is also recognized as Hadaka-Jime-San in Danzan Ryu jujitsu's twenty-five techniques in the Shimete list. Danzan Ryu also recognizes the Guillotine choke as Hadaka-Jime-Ichi. But the principle is the same as Jiu-Jitsu's ground version.

Included systems
Systems: Lists:
 * Kodokan Judo, Judo Lists
 * Danzan Ryu jujitsu, Danza Ryu Lists
 * The Canon Of Judo
 * Judo technique

Hasami-jime
Kyuzo Mifune demonstrates Hasami-Jime in The Essence of Judo and is described in The Canon Of Judo.*

Others
Danzan Ryu enumerates three versions of Hadaka-Jime:

 * 1. Ichi (one): Standing neck-break. Two versions:
 * Neck twist
 * Guillotine
 * A version of the guillotine, Mae-Hadaka-Jime, is also described in The Canon Of Judo, an authoritative work that covers the history of judo and its predecessor jujutsu.

 * 2. Ni (two): Choke with forearm. This is an air choke with the forearm pressing on the throat.
 * 3. San (three): Figure-4 choke with forearm. This is a blood choke with the forearms and biceps pressing and the sides of the neck.

"Sleeper hold" in professional wrestling
The Sleeper Hold was originated in professional wrestling by Evan Lewis in the 1880s when pro wrestling was still a legitimate contest. Lewis earned the nickname "Strangler" for his use of the hold and was an accomplished catch wrestler using the hold defeating Ernst Roeber for the world championship before eventually losing the title to Martin Burns. In the southeastern United States this move was also known as the Charleston Choke.

Modern pro wrestling's first "sleeper hold", technically different from a choke, which is a compression of the throat and/or adam's apple, is thought to have been performed by Jim Londos on 29 June 1931. Suspicion abounded as to the nature of Londos' move (which had looked suspiciously like a choke against the windpipe); however, Londos was quoted the next day in The New York Sun as simply having performed "a new hold I perfected which shuts off the jugular vein."

Though Londos' original move may or may not have been inspired by judo's "hadaka jime", pro-wrestling's sleeper and a rear naked choke both share a similar style of execution. However, in order for the sleeper to be used in the modern performance art-related world of pro-wrestling, the leverage arm is positioned in a relaxed state so the hold is not fully applied.

It is more realistically used by All Elite Wrestling wrestler Samoa Joe (whose wrestling move-set is closer to mixed martial arts). The move has become more of a staple among independent wrestlers, as well as the Japanese wrestlers with the "strong style" of the sport; the most notable being former MMA star Minoru Suzuki.

Catch wrestling's sleeper
In modern catch wrestling circles, the term sleeper hold refers to a variation of the rear naked choke in which the individual performing the hold snakes the leverage arm across the opponent's throat (in the same manner as the traditional rear naked choke) and grasps their opposite shoulder, rather than the biceps. The opposite hand is also placed against the base of the opponent's skull in the form of a closed Hammer Fist, or on top of the head. The attacking wrestler then squeezes their elbows together, pushes forward with the hammer fist (if used), and crunches forward with the abdominal muscles, producing an extremely tight and fast-acting choke.

Safe application
This choke, in either the figure-four or clasped-hand variation, is an extremely dangerous technique if used thoughtlessly or improperly. When applied as a blood choke in particular, it immediately reduces the supply of oxygen to the brain, leading (as mentioned above) to unconsciousness and ultimately (if not released) to brain damage or death. It is imperative, when using this technique, to be completely aware of your opponent's physical state, and to release the choke at any sign of your opponent losing consciousness. From the sport's inception, no fatalities have been reported as due to choking in judo.

title: Rear naked choke


text:
Power-knowledge

In critical theory, power-knowledge is a term introduced by the French philosopher Michel Foucault (le savoir-pouvoir). According to Foucault's understanding, power is based on knowledge and makes use of knowledge; on the other hand, power reproduces knowledge by shaping it in accordance with its anonymous intentions. Power creates and recreates its own fields of exercise through knowledge.

The relationship between power and knowledge has been always a central theme in the social sciences.

Foucault's conception
Foucault was an epistemological constructivist and historicist. Foucault was critical of the idea that humans can reach "absolute" knowledge about the world. A fundamental goal in many of Foucault's works is to show how that which has traditionally been considered as absolute, universal and true in fact is historically contingent. To Foucault, even the idea of absolute knowledge is a historically contingent idea. This does not, however, lead to epistemological nihilism; rather, Foucault argues that people "always begin anew" when it comes to knowledge.

Foucault incorporated mutuality into his neologism power-knowledge, the most important part of which is the hyphen that links the two aspects of the integrated concept together (and alludes to their inherent inextricability).

In his later works, Foucault suggests that power-knowledge was later replaced in the modern world, with the term governmentality which points to a specific mentality of governance.

Subsequent developments
While in most of the 20th century the term ‘knowledge’ has been closely associated with power, in the last decades ‘information’ has become a central term as well. With the growing use of big-data, information is increasingly seen as the means to generate useful knowledge and power.

One of the recently developed model, known as the Volume and Control Model, describes how information is capitalized by global corporations and transforms into economic power. Volume is defined as the informational resources—the amount and diversity of information and the people producing it. Control is the ability to channel the interaction between information and people through two competing mechanisms: popularization (information relevant to most people), and personalization (information relevant to each individual person).

According to this understanding, knowledge is never neutral, as it determines force relations. The notion of power-knowledge is therefore likely to be employed in critical, normative contexts. One example of the implications of power-knowledge is Google’s monopoly of knowledge, its PageRank algorithm, and its inevitable commercial and cultural biases around the world, which are based on the volume and control principles. A recent study shows, for example, the commercial implications of Google Images algorithm, as all search results for the term 'beauty' in different languages predominantly yield images of young white women.

title: Power-knowledge


text:
User talk:Stezton

Fair use rationale for File:HamburgerHelperHand.jpeg
Thanks for uploading or contributing to File:HamburgerHelperHand.jpeg. I notice the file page specifies that the file is being used under fair use but there is not a suitable explanation or rationale as to why each specific use in Wikipedia constitutes fair use. Please go to the file description page and edit it to include a fair use rationale.

If you have uploaded other fair use media, consider checking that you have specified the fair use rationale on those pages too. You can find a list of 'file' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "File" from the dropdown box. Note that any non-free media lacking such an explanation will be deleted one week after they have been tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you. Sfan00 IMG (talk) 10:36, 22 October 2010 (UTC)

File:Stezton.jpg listed for deletion
A file that you uploaded or altered, File:Stezton.jpg, has been listed at Files for deletion. Please see the to see why this is (you may have to search for the title of the image to find its entry), if you are interested in it not being deleted. Thank you. Calliopejen1 (talk) 15:36, 4 October 2011 (UTC)

Orphaned non-free image File:RygarNEScover.jpg
 Thanks for uploading File:RygarNEScover.jpg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently orphaned, meaning that it is not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

PLEASE NOTE:

 * I am a bot, and will therefore not be able to answer your questions. If you have a question, place a template, along with your question, beneath this message.
 * I will remove the request for deletion if the file is used in an article once again.
 * If you receive this notice after the image is deleted, and you want to restore the image, click here to file an un-delete request.
 * To opt out of these bot messages, add  to your talk page.
 * If you believe the bot has made an error, please turn it off here and leave a message on my owner's talk page.

Thank you. DASHBot (talk) 05:47, 30 December 2011 (UTC)

Non-free rationale for File:TV tycoon.jpg
Thanks for uploading or contributing to File:TV tycoon.jpg. I notice the file page specifies that the file is being used under non-free content criteria, but there is not a suitable explanation or rationale as to why each specific use in Wikipedia is acceptable. Please go to the file description page, and edit it to include a non-free rationale.

If you have uploaded other non-free media, consider checking that you have specified the non-free rationale on those pages too. You can find a list of 'file' pages you have edited by clicking on the "my contributions" link (it is located at the very top of any Wikipedia page when you are logged in), and then selecting "File" from the dropdown box. Note that any non-free media lacking such an explanation will be deleted one week after they have been tagged, as described on criteria for speedy deletion. If the file is already gone, you can still make a request for undeletion and ask for a chance to fix the problem. If you have any questions, please ask them at the Media copyright questions page. Thank you. Sfan00 IMG (talk) 16:44, 27 June 2012 (UTC)

Disambiguation link notification for June 8
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Cauliflower Alley Club, you added a link pointing to the disambiguation page Melissa Anderson (check to confirm | fix with Dab solver). Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ* Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 08:59, 8 June 2014 (UTC)

ArbCom elections are now open!
MediaWiki message delivery (talk) 13:08, 23 November 2015 (UTC)

ArbCom elections are now open!
MediaWiki message delivery (talk) 13:33, 23 November 2015 (UTC)

Orphaned non-free image File:Krabbypatty.JPG
 Thanks for uploading File:Krabbypatty.JPG. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in the criteria for speedy deletion. Thank you. --B-bot (talk) 02:31, 14 March 2016 (UTC)

Files for discussion/2016 June 14
I saw that you uploaded the front cover of the North American release at least ten years ago. I uploaded it without realizing the origins. Anyway, I invite you to the latest discussion about front covers of Tales of Eternia. Join the discussion. --George Ho (talk) 08:16, 15 June 2016 (UTC)

Orphaned non-free image File:OurTimeInEden.jpeg
Thanks for uploading File:OurTimeInEden.jpeg. The image description page currently specifies that the image is non-free and may only be used on Wikipedia under a claim of fair use. However, the image is currently not used in any articles on Wikipedia. If the image was previously in an article, please go to the article and see why it was removed. You may add it back if you think that that will be useful. However, please note that images for which a replacement could be created are not acceptable for use on Wikipedia (see our policy for non-free media).

Note that any non-free images not used in any articles will be deleted after seven days, as described in section F5 of the criteria for speedy deletion. Thank you. --B-bot (talk) 03:38, 13 November 2020 (UTC)

title: User talk:Stezton


text:
File:Enigma Return to Innocence single cover.jpg

Summary
Single cover of "Return to Innocence" by Enigma (musical project).

Fair use in Return to Innocence
Though this image is subject to copyright, its use is covered by the U.S. fair use laws because:
 * 1) It's a low resolution copy of a CD/album cover.
 * 2) It doesn't limit the copyright owner's rights to sell the CD/album in any way, in fact, it may encourage sales.
 * 3) Because of the low resolution, copies could not be used to make illegal copies of the album artwork on another CD.
 * 4) The image is itself a subject of discussion in the article or used in the infobox thereof.
 * 5) The image on the cover is significant because it was made by a famous artist.

Source

 * 1) Derived from a digital capture (scan/photo) of the album/CD cover (creator of this digital version is irrelevant as the copyright in all equivalent images is still held by the same party). Copyright held by the record company or the artist. Claimed as fair use regardless.


text:
Red locust

The red locust (Nomadacris septemfasciata) is a large grasshopper species found in sub-Saharan Africa. Its name refers to the colour of its hind wings. It is sometimes called the criquet nomade in French, due to its nomadic movements in the dry season. When it forms swarms, it is described as a locust.

Nomadacris septemfasciata is in the family Acrididae and is the only member of the genus Nomadacris. The genus Nomadacris was erected in 1923 by Boris Uvarov and the species was named originally as Acridium septemfasciatum by Jean Guillaume Audinet-Serville in 1838. It is placed in the subfamily Cyrtacanthacridinae, the bird locusts. Other species previously placed in Nomadacris are now considered part of the genus Patanga.

Adults
The overall colour of adult insects is a mixture of light beige and brown. They have seven brown transverse bands on the elytra, justifying the species name septemfasciata. The pronotum has two brown lateral bands.

Males are 60 – long; females are 60 – long.

Nymphs
Unlike adults, the colour of immature insects varies depending on their phase. When solitary, they can be green or brown; when in large numbers (gregarious), they are bright yellow and red-brown with black markings.

Ecology
Red locusts actively seek out moist environments such as seasonal floodplains. Grains are their primary food source, so grassy lowlands are prime habitat. They also like spending time in trees and thus prefer some tree cover.

Red locusts are sedentary when ample shelter, perches, and food are available. In dry years, when the amount of suitable habitat is reduced, population densities increase. If the population density increases past a threshold, the locusts transform into their gregarious phase, changing their behaviour and anatomy. When gregarious, red locusts keep together in large swarms and fly with the wind in daylight hours, looking for more food. The higher temperatures during daylight enable gregarious locusts to travel longer distances by flying longer and higher, aided by thermal lift. A swarm rarely moves more than 20–30 km in a day. In contrast, solitary locusts prefer to fly in the dark and do so alone.

Compared to their solitary phase, gregarious red locusts also have:
 * reduced lifespan
 * more markings
 * six instar stages rather than seven
 * longer sexual maturation
 * larger and heavier young, although they lay fewer eggs

Swarming females often lay eggs at night. Their young immediately behave gregariously and are capable of "hopping" hundreds of metres every day.

Outbreaks
Outbreak areas have been identified in Zambia, Tanzania, Malawi, Madagascar, and Réunion. In the Sahel, the species is observed on a more incidental basis in Cape Verde, the central Niger River delta in Mali, and around Lake Chad. Large swarms attacked the KwaZulu-Natal region which contributed to creating conditions which favoured the 1890s African rinderpest outbreak. The last widespread plague occurred from 1930 to 1944, when almost all of southern Africa was invaded.

After unsuccessful efforts to control the locusts through environmental modifications, chemical agents are currently being used. A biological product based on an entomopathogenic fungus, Metarhizium acridum, is now available (see desert locust). It has been successfully tested on both nymphs and adults of the red locust. However, over recent years, a new mechanism to control pests was created. The Integrated pest management (IPM) is a combination of environmentally friendly methods that together can be used effectively as a pest management strategy.

title: Red locust


text:
FCM Bacău

Asociația Sportivă a Suporterilor FCM 1950 Bacău (also known as ASS FCM 1950 Bacău, FCM 1950 Bacău or FCM Bacău) is a Romanian football club based in Bacău, Bacău County, Moldavia. Founded in 1950 as Dinamo Bacău, the club spent 42 seasons in the top-flight of the Romanian football, winning a Romanian League Cup and qualifying for European competitions such as the Cup Winners' Cup and the Intertoto Cup.

In the early 2010s, the club entered in a shadowy cone due to the conflict between the team's owner, Dumitru Sechelariu (former mayor of Bacău) and the newly elected mayor, who chose to retire the public financing of the team and to sustain SC Bacău. Health problems, and subsequently, the premature death of Dumitru Sechelariu in the early 2013, multiplied the existing financial problems of the club. This caused FCM Bacău to withdraw from beginning of the 2013–14 Liga III season, before dissolving later on.

In 2017, the Supporters Association of FCM Bacău, supported by Sergiu Sechelariu, brother of Dumitru and legal owner of the "FCM 1950 Bacău brand", started a collaboration with Gauss Bacău (former SC Bacău) team also left in the meantime without financing by the municipality, but the collaboration broken in the summer of 2018 and after a year of inactivity, the fans (supported again by Sechelariu's brother) started a new project named ASS FCM 1950 Bacău and enrolled the senior squad in the Liga IV.

Early years (1950–1992)
FCM Bacău was founded in 1950 as Dinamo Bacău under the Ministry of Internal Affairs with other clubs which bore the name "Dinamo". Its management decided to separate from the ministry, renaming it Sport Club Bacău and adding athletics and tennis.

The team first appeared in Romania's first league during the 1956 season, after which they were then relegated to the second division. Returning to Divizia A, they finished fifth in 1968–69 and qualified for the Fairs Cities' Cup (the precursor of the UEFA Cup and the UEFA Europa League). At the time, Bacău's roster included Emerich Dembrovschi, Nicolae Vătafu, Petre Băluță, Artistică Ghiță, and Daniel Ene. Bacău advanced to the second round against Skeid Fotball, which had eliminated West Germany's 1860 Munich. Bacău advanced again, defeating the Scottish club Kilmarnock F.C. In the quarter-finals, Bacău played Arsenal F.C. club.

After making the quarterfinals of the Fairs Cities' Cup, the băcăuanii also did well in the domestic championship; at the end of the 1972–73 season, SC Bacău (the club's name from 1970 to 1990) finished in fourth place (the best in club history). Sport Club played well in the Cupa României, where, after the Romanian Revolution, they reached the final at the end of the 1990–91 season before losing 2–1 to Universitatea Craiova. Universitatea Craiova was also the winner of Divizia A that season, which allowed the yellow-and-blues to qualify for the second and final time in a European competition (the UEFA Cup). FC Bacău was drawn to meet Werder Bremen, which would defeat AS Monaco 2–0 in the Cup Winners' Cup. Werder Bremen was a tall, strong, cosmopolitan squad; FC Bacău was a little-known team with serious financial problems.

Sechelariu era (1992–2014)
From 1992 to 2006, the team remained in Divizia A as Selena, AS and FCM; Dumitru Sechelariu was its owner. It was a period of relative growth; the team finished 11th in 1995–96 (when they won 5–1 at Steaua Stadium), fifth in 1996–97, 10th in 1997–98, fifth in 1998–99, and eighth in 1999–2000. They were relegated in the summer of 2001 after a relegation play-off against Farul Constanța. The 2001–02 season began with high hopes, great investments and a 4–2 win against Dinamo București before a sixth place. After 2002, FCM Bacău was in the lower part of the tables and was relegated to Liga II at the end of the 2005–06 season. Sechelariu referred to FCM Bacău as "my child", "dear", but also "disabled".

At the end of the 2006–07 season, the team finished in fifth place; the following season, they were one step away from relegation to the third tier. For the 2009–10 season, the team focused on promotion to Liga I; due to financial problems and misunderstandings between Dumitru Sechelariu and the municipal council, FCM was relegated to Liga III after forfeiting two matches.

The municipality of Bacău registered the team for the following season in Liga III as SCM Bacău. On 9 June 2010, it was announced that a new club would be developed by the municipality; Sechelariu became a minority shareholder. The new management of the yellow-and-blues decided to change their name to SC FCM Bacău SA and terminate the contracts of former AS FCM Bacău players. FCM Bacău was promoted to Liga II in 2011, finishing seventh the following season. Before the next season, the players left the club for financial reasons (most for FC Botoșani) and Sechelariu transferred the club entirely to the municipality. With the team facing relegation to the third league, the municipality decided to stop investing in the club and re-direct public financing to CS Mesagerul Bacău (which would be renamed SC Bacău). After Sechelariu's declining health and death in early 2013, the club withdrew from the league at the start of the season and was dissolved.

Supporters, the last hope (2017–2020)
The Supporters Association of FCM Bacău, supported by Sergiu Sechelariu (Dumitru's brother and owner of the FCM 1950 Bacău brand), began a collaboration with Gauss Bacău (the former SC Bacău) in 2017. The collaboration broke down during the summer of 2018; after a year of inactivity, fans (supported again by Sergiu Sechelariu) began the ASS FCM 1950 Bacău. They enrolled the senior squad in Liga IV, but the team was again dissolved at the end of the 2019–20 season.

Grounds

Until 1966 FCM Bacău (named Dinamo Bacău) used to play its home matches on Steaua Roșie Stadium, with a capacity of 5,000 people, but moved subsequently on the Municipal Stadium in Bacău, with a capacity of 17,500 seats. Seen as a coquettish stadium of the country, especially during Sechelariu's era, when the owner of the team Dumitru Sechelariu renovated, modernized it and assured the installation of a floodlight system. Between 2001 and 2004, the stadium was named as Dumitru Sechelariu, after the name of the eccentric businessman, mayor of Bacău and owner of FCM. Death of Sechelariu it meant broadly the death of football from Bacău, after FCM, the stadium was also abandoned, being the victim of an unsuccessful modernization project. The stadium which is situated in the center of the city and was only some time ago the home of FCM is now a ruin.

After the re-foundation as ASS FCM Bacău, the club has to play its home matches on Baza Sportivă Nautică Șerbănești, with a capacity of only 200 people.

Support
FCM Bacău has many supporters in Bacău and especially in Bacău County. The ultras groups of FCM Bacău are known as Taurii furioși, Best and Ultra Boys. The three groups merged in 2010 and form FCM 1950 Bacău, group that developed subsequently in an association that managed to bring back to life the club from the city of George Bacovia. In the past were also another ultras groups such as RSB, Prima-Linie or FRT Bacău.

FCM Bacău fans have an intense rivalry with the supporters of Ceahlăul Piatra Neamț, which are known under the name of Urșii carpatini.

Rivalries
The most important rivalry for FCM Bacău is the one against Ceahlăul Piatra Neamț. This match is known as the Derby of Moldavia or Il Classico. Over time, FCM had important rivalries with other teams, such as Steaua București, Dinamo București or Rapid București, as well as some regional ones and even local, for example against SC Bacău.

Leagues

 * Liga I
 * Winners (0):, Best finish: 4th 1972–73
 * Liga II
 * Winners (4): 1955, 1966–67, 1974–75, 1994–95
 * Runners-up (3): 1954, 1957–58, 1964–65
 * Liga III
 * Winners (1): 2010–11
 * Liga IV – Bacău County
 * Runners-up (1): 2019–20

Cups

 * Cupa României
 * Winners (0):
 * Runners-up (1): 1990–91
 * Cupa Ligii:
 * Winners (1): 1998

Biggest victories and defeats
'

 * Biggest Home Win:
 * 6–0 vs. Universitatea Craiova, 7 December 1988
 * Biggest Home Loss:
 * 0–8 vs. Steaua București, 6 May 1956
 * Biggest Away Win:
 * 4–0 vs. Bihor Oradea, 18 October 1969
 * 5–1 vs. Steaua București, 17 August 1996
 * Biggest Away Loss:
 * 0–8 vs. Steaua București, 30 November 1969
 * Highest Scoring:
 * 6–4 vs. Sportul Studențesc București, 27 November 1988
 * 3–7 vs. Dinamo București, 19 September 2003

 * Highest Scoring Draw:
 * 4–4 vs. Steaua București, 20 October 1979
 * Most Goals Scoring While Losing:
 * 3–4 vs. Progresul București, 9 June 1963
 * 3–4 vs. Universitatea Craiova, 11 November 1973
 * 3–4 vs. Jiul Petroșani, 18 September 1982
 * 3–4 vs. Argeș Pitești, 30 March 1986
 * 3–5 vs. Sportul Studențesc București, 25 June 1987
 * 3–5 vs. Victoria București, 9 October 1988
 * 3–5 vs. Bihor Oradea, 17 September 1989
 * 3–4 vs. Steaua București, 7 August 2000
 * 3–7 vs. Dinamo București, 19 September 2003

Longest Streaks
'

Wins and Losses

 * Longest Winning Streak (5):
 * From Round 19 of 1962–63 to Round 23 of 1962–63
 * Longest Unbeaten Streak (14):
 * From Round 34 of 1997–98 to Round 13 of 1998–99
 * Longest Drawing Streak (8):
 * From Round 7 of 1979–80 to Round 14 of 1979–80
 * Longest Not Drawing Streak (39):
 * From Round 33 of 1992–93 to Round 3 of 1996–97
 * Longest Winless Streak (15):
 * From Round 16 of 2005–06 to Round 30 of 2005–06
 * Longest Losing Streak (13):
 * From Round 17 of 2005–06 to Round 29 of 2005–06

 * Longest Home Winning Streak (13):
 * From Round 3 of 1968–69 to Round 28 of 1968–69
 * Longest Home Unbeaten Streak (43):
 * From Round 20 of 1967–68 to Round 18 of 1970–71
 * Longest Home Drawing Streak (4):
 * From Round 7 of 1979–80 to Round 14 of 1979–80
 * Longest Home Not Drawing Streak (19):
 * From Round 34 of 1992–93 to Round 2 of 1996–97
 * Longest Home Winless Streak (7):
 * From Round 16 of 2005–06 to Round 29 of 2005–06
 * Longest Home Losing Streak (6):
 * From Round 18 of 2005–06 to Round 29 of 2005–06

 * Longest Away Winning Streak (3):
 * From Round 20 of 1962–63 to Round 25 of 1962–63
 * Longest Away Unbeaten Streak (6):
 * From Round 1 of 1998–99 to Round 12 of 1998–99
 * Longest Away Drawing Streak (4):
 * From Round 8 of 1979–80 to Round 13 of 1979–80
 * Longest Away Not Drawing Streak (29):
 * From Round 20 of 1961–62 to Round 21 of 1967–68
 * Longest Away Winless Streak (45):
 * From Round 2 of 2003–04 to Round 30 of 2005–06
 * Longest Away Losing Streak (14):
 * From Round 27 of 1969–70 to Round 22 of 1970–71

Scoring and Conceding

 * Longest Scoring Streak (10):
 * From Round 16 of 1960–61 to Round 25 of 1960–61
 * From Round 33 of 1981–82 to Round 8 of 1982–83
 * From Round 31 of 1997–98 to Round 6 of 1998–99
 * Longest Clean Sheets Streak (5):
 * From Round 9 of 2002–03 to Round 13 of 2002–03
 * Longest Scoreless Streak (6):
 * From Round 9 of 1997–98 to Round 14 of 1997–98
 * Longest Conceding Streak (25):
 * From Round 5 of 2005–06 to Round 29 of 2005–06

 * Longest Home Scoring Streak (26):
 * From Round 23 of 1995–96 to Round 3 of 1997–98
 * Longest Home Clean Sheets Streak (9):
 * From Round 26 of 1969–70 to Round 14 of 1970–71
 * From Round 18 of 1984–85 to Round 33 of 1984–85
 * Longest Home Scoreless Streak (4):
 * From Round 19 of 2003–04 to Round 25 of 2003–04
 * Longest Home Conceding Streak (13):
 * From Round 6 of 2005–06 to Round 29 of 2005–06

 * Longest Away Scoring Streak (7):
 * From Round 26 of 1997–98 to Round 5 of 1998–99
 * Longest Away Clean Sheets Streak (3):
 * From Round 15 of 1960–61 to Round 18 of 1960–61
 * From Round 24 of 1968–69 to Round 27 of 1968–69
 * From Round 28 of 2002–03 to Round 2 of 2003–04
 * Longest Away Scoreless Streak (9):
 * From Round 28 of 1991–92 to Round 9 of 1992–93
 * Longest Away Conceding Streak (31):
 * From Round 22 of 1983–84 to Round 15 of 1985–86

Notable former players
The footballers enlisted below have had international cap(s) for their respective countries at junior and/or senior level and/or more than 100 caps for FCM Bacău.

 * Romania
 * 🇷🇴 Vasile Alexandru
 * 🇷🇴 Florian Ambru
 * 🇷🇴 Ștefan Apostol
 * 🇷🇴 Vasile Ardeleanu
 * 🇷🇴 Sorin Avram
 * 🇷🇴 Eugen Baciu
 * 🇷🇴 Dragu Bădin
 * 🇷🇴 Valentin Bădoi
 * 🇷🇴 Daniel Bogdan
 * 🇷🇴 Radu Ciobanu
 * 🇷🇴 Cristian Ciocoiu
 * 🇷🇴 Corneliu Codreanu
 * 🇷🇴 Narcis Coman
 * 🇷🇴 Mircea Constantinescu
 * 🇷🇴 Andrei Cristea
 * 🇷🇴 Marius Croitoru
 * 🇷🇴 Cătălin Cursaru
 * 🇷🇴 Daniel David
 * 🇷🇴 Emerich Dembrovschi
 * 🇷🇴 Marius Doboș
 * 🇷🇴 Gheorghe Ene
 * 🇷🇴 Florin Ganea
 * 🇷🇴 Dudu Georgescu
 * 🇷🇴 Dorin Goian
 * 🇷🇴 Viorel Ignătescu
 * 🇷🇴 Silviu Iorgulescu
 * 🇷🇴 Vasile Jercălău
 * 🇷🇴 Ionuț Mihălăchioaie
 * 🇷🇴 Lică Movilă
 * 🇷🇴 Vlad Munteanu
 * 🇷🇴 Lică Nunweiller
 * 🇷🇴 Nicolae Oaidă
 * 🇷🇴 Florin Petcu
 * 🇷🇴 Cornel Popa
 * 🇷🇴 Cristian Popovici
 * 🇷🇴 Florin Prunea
 * 🇷🇴 Narcis Răducan
 * 🇷🇴 Răzvan Raț
 * 🇷🇴 Vasile Simionaș
 * 🇷🇴 Vasile Șoiman
 * 🇷🇴 Costel Solomon
 * 🇷🇴 Marian Tănasă
 * 🇷🇴 Ion Țîrcovnicu
 * 🇷🇴 Sorin Trofin
 * Moldova
 * Alexei Scala
 * Iurie Scala

Notable former managers

 * 🇷🇴 Florian Ambru
 * 🇷🇴 Gheorghe Constantin
 * 🇷🇴 Nicolae Dumitru
 * 🇷🇴 Florin Halagian
 * 🇷🇴 Traian Ionescu
 * 🇷🇴 Valeriu Neagu
 * 🇷🇴 Mircea Nedelcu
 * 🇷🇴 Angelo Niculescu
 * 🇷🇴 Constantin Teașcă
 * 🇷🇴 Costel Orac
 * 🇷🇴 Gheorghe Poenaru
 * 🇷🇴 Cristian Popovici
 * 🇷🇴 Constantin Rădulescu
 * 🇷🇴 Andrei Sepci
 * 🇷🇴 Nicolae Vătafu

title: FCM Bacău


text:
TNA Lockdown

Lockdown was a professional wrestling event held by the American professional wrestling promotion TNA Wrestling. The event was first held in 2005 and was considered one of the flagship events in the company (alongside Slammiversary and Bound for Glory). The theme of the event was that the entire card would be contested inside a steel cage. Other matches on the card featured additional gimmicks added on to the steel cage format, such as the signature Lethal Lockdown match (a variant on the WarGames match), and the Xscape and "Queen of the Cage" matches.

Originally, Lockdown was to have only two cage matches to highlight the name; the 2013 event was the only one to follow this format. With the exception of the 2005 and 2006 events, Lockdown has been held outside the Impact Zone in Orlando, Florida. The first ten events were held on Pay-per-view, while the last two events were broadcast as special episodes of Impact's weekly television series. On January 24, 2020, Impact announced the return of Lockdown as an Impact Plus special, to be held on March 28, 2020, but the event was cancelled due to the COVID-19 pandemic.

History
The inaugural Lockdown event took place on April 24, 2005, at the TNA Impact! Zone in Orlando, Florida. The event started with Apolo and Sonny Siaki facing Chris Candido and Lance Hoyt in a Six Sides of Steel Cage match. During the match, Candido suffered a leg injury and was helped to the back as Apollo and Hoyt won the match. Candido was later diagnosed with a dislocated ankle, broken tibia, and a broken fibula that required surgery. On April 28, after the surgery, Candido was rushed to the hospital after he collapsed where he died a short time later due to a blood clot from the surgery. On May 15, 2005, at the inaugural Hard Justice event, TNA paid tribute to Candido with a ten-bell salute.

Lockdown remained a regular TNA's pay-per-view until the last event, which took place on January 30, 2016, and aired on tape delay on February 23, at the Wembley Arena in London, England.

Featured matches
Over the years, Lockdown has become a featured PPV in Impact Wrestling's monthly schedule, several gimmick matches have become recurring highlights of the show. These matches are intended to provide a different "flavor" to the show as opposed to a simple eight cage match card.

Lethal Lockdown
The first match ever announced for a Lockdown pay per view was the Lethal Lockdown, a variant of the WarGames match popularized in World Championship Wrestling. The match features a multi-man competition in which opponents from each team enter in alternating fashion. Victory can only be gained after everyone has entered the cage. The match has evolved over the years, developing from a three-on-three match (2005) to a four-on-four (2006, 2009, 2010-2011 and 2014) to a five-on-five (2007-2008, 2012-2013). Since 2006, the match also includes a roof to the cage, making it the only match with such a feature in TNA, until TNA introduced The Asylum.

Xscape Match
The second annually featured match on a Lockdown PPV was the Xscape match. Consisting of a multi-stage, multi-wrestler competition, the rules involve wrestlers eliminating each other by pinfall or submission. Once the competition is down to two wrestlers, the two remaining competitors attempt to escape the cage by climbing out over the top or through the door. The second stage of this match is based on the concept of the Blassie cage match.

Queen of the Cage
Introduced in 2008, the Queen of the Cage match has been held at 2 Lockdown PPV's, and it features the TNA Knockouts. The match when it debuted began as similar to a reverse-battle royal involving eight wrestlers. The first two wrestlers that entered the cage then competed in a one-on-one match that was won via pin fall or submission. The winner became the number one contender for the TNA Women's Knockout Championship. In 2009, the match was a four-way. Since then, the matches have not been added in the pay-per-view any more.

title: TNA Lockdown


text:
Peter Carl Goldmark

Peter Carl Goldmark (born Péter Károly Goldmark; December 2, 1906 – December 7, 1977) was a Hungarian-American engineer who, during his time with Columbia Records, was instrumental in developing the long-playing microgroove 33$1/3$ rpm phonograph disc, the standard for incorporating multiple or lengthy recorded works on a single disc for two generations. The LP was introduced by Columbia's Goddard Lieberson in 1948. Lieberson was later president of Columbia Records from 1956–1971 and 1973–1975. According to György Marx, Goldmark was one of The Martians.

Early life
Goldmark married Frances Trainer, whom he later divorced. Together they had four children; three sons: Peter Jr., Christopher, Andrew and one daughter: Frances. After divorcing Frances Trainer, Goldmark married Diane Davis and had two more children: Jonathan and Susan.

Career
In addition to his work on the LP record, Goldmark developed field-sequential color technology for color television while at CBS. The system, first demonstrated on August 29, 1940, and shown to the press on September 3 used a rapidly rotating color wheel that alternated transmission in red, green and blue. The system transmitted on 343 lines, about 100 less than a black and white set, and at a different field scan rate, and thus was incompatible with television sets currently on the market without an adapter.

Although CBS did broadcast in color with the Goldmark system in 1950–1951, the "compatible color" technology developed for RCA and NBC (by a team led by Richard Kell, George H. Brown and others) was compatible with existing black and white TVs. Goldmark and others have pointed out that the CBS color wheel system did provide better picture quality (although lower image resolution) than RCA's system, but the compatibility problem proved its downfall. An improved RCA/NBC color system submitted in July 1953 became the industry standard chosen by the Federal Communications Commission (FCC) in December 1953. Ironically, cameras using the color wheel system continued to be used for scientific research for several more decades, including the color lunar surface TV cameras during all the 1970s NASA Apollo Moon landings.

After the success of the LP record, Goldmark spent the next two decades at CBS Laboratories working on various inventions, chief of which was EVR, the Electronic Video Recorder. This futuristic home video playback device used reels of film stored in plastic cassettes to electronically store audio and video signals, and was first announced in 1967. A B&W prototype was demonstrated in 1969 (promising color playback in future models), but the invention floundered when it proved to be difficult and costly to manufacture. CBS was also concerned about the potential of competition from home video devices, particularly those that could record — a fear that eventually proved prescient.

Later life
Goldmark was awarded the Elliott Cresson Medal in 1969. He received the Golden Plate Award of the American Academy of Achievement in 1970.

On November 22, 1977, President Jimmy Carter presented Goldmark with the National Medal of Science "For contributions to the development of the communication sciences for education, entertainment, culture, and human service."

Goldmark died at the age of 71 in an automobile accident on December 7, 1977, in Westchester County, New York.

General references

 * Coleman, Mark (2005) PLAYBACK: From the Victrola to MP3, 100 Years of Music, Machines and Money, Published by Da Capo Press (ISBN 0-306-81390-4)
 * Fisher and Fisher, "The Color War", Invention and Technology (Winter 1997)
 * Goldmark, Peter (1973) Maverick Inventor: My Turbulent Years at CBS, published by Saturday Review Press (ISBN 0841500460)
 * Reitan, Jr., Edward Howrd, "Ed Reitan's Color Television History", retrieved July 1, 2007.

title: Peter Carl Goldmark


text:
Talk:Cecily Lefort

date of death
How can she have been gassed on 1 May when the camp was taken over by the Soviets on 30 April ( according to the Ravensbruck article )--jrleighton 10:36, 20 August 2005 (UTC)

No sources either.

–This short biography has her execution in February 1945, not May. I don't know how reliable it is. http://www.64-baker-street.org/agents/agent_waaf_cecily_lefort.html Cravenmonket 23:07, 5 March 2007 (UTC)

-- Heroines of SOE does not contain a date of death for Cecily (and it does include them for as many women of F-section as possible). Moira Paul (talk) 14:41, 13 June 2019 (UTC)

WikiProject class rating
This article was automatically assessed because at least one article was rated and this bot brought all the other ratings up to at least that level. BetacommandBot 02:41, 27 August 2007 (UTC)

Brittany not in Britain
"she fled occupied France and went to England where she and her husband made their home in Brittany" makes no sense. Brittany *was* part of occupied France.75.35.74.21 (talk) 00:04, 2 May 2009 (UTC)Nancy Raffman

 * They had a home in Brittany but escaped to England, and then allowed SOE to use their (now vacant) home in Brittany for purposes useful to the Allied cause. SOE and the French Resistance used their home as a base in occupied Brittany. — Preceding unsigned comment added by 80.7.147.13 (talk) 13:48, 1 January 2014 (UTC)

title: Talk:Cecily Lefort


text:
Talk:Cingalese

I'm not sure if this term is just an ethnic descriptor or if it is a racial slur.--nixie 10:37, 20 August 2005 (UTC)

title: Talk:Cingalese