text:
Underground storage tank

An underground storage tank (UST) is, according to United States federal regulations, a storage tank, including any underground piping connected to the tank, that has at least 10 percent of its volume underground.

Definition & Regulation in U.S. federal law
"Underground storage tank" or "UST" means any one or combination of tanks including connected underground pipes that is used to contain regulated substances, and the volume of which including the volume of underground pipes is 10 percent or more beneath the surface of the ground. This does not include, among other things, any farm or residential tank of 1,100 gallons or less capacity used for storing motor fuel for noncommercial purposes, tanks for storing heating oil for consumption on the premises, or septic tanks.

USTs are regulated in the United States by the U.S. Environmental Protection Agency to prevent the leaking of petroleum or other hazardous substances and the resulting contamination of groundwater and soil. In 1984, U.S. Congress amended the Resource Conservation Recovery Act to include Subtitle I: Underground Storage Tanks, calling on the U.S. Environmental Protection Agency (EPA) to regulate the tanks. In 1985, when it was launched, there were more than 2 million tanks in the country and more than 750,000 owners and operators. The program was given 90 staff to oversee this responsibility. In September 1988, the EPA published initial underground storage tank regulations, including a 10-year phase-in period that required all operators to upgrade their USTs with spill prevention and leak detection equipment.

For USTs in service in the United States, the EPA and states collectively require tank operators to take financial responsibility for any releases or leaks associated with the operation of those below ground tanks. As a condition to keep a tank in operation a demonstrated ability to pay for any release must be shown via UST insurance, a bond, or some other ability to pay.

EPA updated UST and state program approval regulations in 2015, the first major changes since 1988. The revisions increase the emphasis on properly operating and maintaining UST equipment. The revisions will help prevent and detect UST releases, which are a leading source of groundwater contamination. The revisions will also help ensure all USTs in the United States, including those in Indian country, meet the same minimum standards. The changes established federal requirements that are similar to key portions of the Energy Policy Act of 2005. In addition, EPA added new operation and maintenance requirements and addressed UST systems deferred in the 1988 UST regulation. The changes:

 * Added secondary containment requirements for new and replaced tanks and piping
 * Added operator training requirements
 * Added periodic operation and maintenance requirements for UST systems
 * Added requirements to ensure UST system compatibility before storing certain biofuel blends
 * Removed past deferrals for emergency generator tanks, field constructed tanks, and airport hydrant systems
 * Updated codes of practice
 * Made editorial and technical corrections.

Tank types
Underground storage tanks fall into four different types:

 * 1) Steel/aluminum tanks, made by manufacturers in most states and conforming to standards set by the Steel Tank Institute.
 * 2) Composite overwrapped, a metal tank (aluminum/steel) with filament windings like glass fiber/aramid or carbon fiber or a plastic compound around the metal cylinder for corrosion protection and to form an interstitial space.
 * 3) Tanks made from composite material, fiberglass/aramid or carbon fiber with a metal liner (aluminum or steel). See metal matrix composite.
 * 4) Composite tanks such as carbon fiber with a polymer liner (thermoplastic). See rotational molding and fibre-reinforced plastic (FRP).

Underground storage tanks for water are traditionally called cisterns and are usually constructed from bricks and mortar or concrete.

Petroleum underground storage tanks
Petroleum USTs are used throughout North America at automobile filling stations and by the US military. Many have leaked, allowing petroleum to contaminate the soil and groundwater and enter as vapor into buildings, ending up as brownfields or Superfund sites. Many USTs installed before 1980 consisted of bare steel pipes, which corrode over time. Faulty installation can also cause structural failure of the tank or piping, causing leaks.

Regulation in the US
The 1984 Hazardous and Solid Waste Amendments to the Resource Conservation and Recovery Act (RCRA) required EPA to develop regulations for the underground storage of motor fuels to minimize and prevent environmental damage, by mandating owners and operators of UST systems to verify, maintain, and clean up sites damaged by petroleum contamination.

In December 1988, EPA regulations asking owners to locate, remove, upgrade, or replace underground storage tanks became effective. Each state was given authority to establish such a program within its own jurisdiction, to compensate owners for the cleanup of underground petroleum leaks, to set standards and licensing for installers, and to register and inspect underground tanks.

Most upgrades to USTs consisted of the installation of corrosion control (cathodic protection, interior lining, or a combination of cathodic protection and interior lining), overfill protection (to prevent overfills of the tank during tank filling operations), spill containment (to catch spills when filling), and leak detection for both the tank and piping.

Many USTs were removed without replacement during the 10-year program. Many thousands of old underground tanks were replaced with newer tanks made of corrosion resistant materials (such as fiberglass, steel clad with a thick FRP shell, and well-coated steel with galvanic anodes) and others constructed as double walled tanks to form an interstice between two tank walls (a tank within a tank) which allowed for the detection of leaks from the inner or outer tank wall through monitoring of the interstice using vacuum, pressure or a liquid sensor probe. Piping was replaced during the same period with much of the new piping being double-wall construction and made of fiberglass or plastic materials.

Tank monitoring systems capable of detecting small leaks (must be capable of detecting a 0.1 gallons-per-hour with a probability of detection of 95% or greater and a probability of false alarm of 5% or less) were installed and other methods were adopted to alert the tank operator of leaks and potential leaks.

U.S. regulations required that UST cathodic protection systems be tested by a cathodic protection expert (minimum every three years) and that systems be monitored to ensure continued compliant operation.

Some industrial owners, who previously stored fuel in underground tanks, switched to above-ground tanks to avoid environmental regulations that require monitoring of fuel storage. Many states, however, do not permit above-ground storage of motor fuel for resale to the public.

The EPA Underground Storage Tank Program is considered to have been very successful. The national inventory of underground tanks has been reduced by more than half, and most of the rest have been replaced or upgraded to much safer standards. Of the approximately one million underground storage tanks sites in the United States as of 2008, most of which handled some type of fuel, an estimated 500,000 have had leaks. , there were approximately 600,000 active USTs at 223,000 sites subject to federal regulation. In 2012, EPA published how to screen buildings vulnerable to petroleum vapor intrusion, and in June 2015, U.S. EPA finally released its "Technical Guide for Assessing and Mitigating the Vapor Intrusion Pathway from Subsurface Vapor Sources to Indoor Air" and "Technical Guide For Addressing Petroleum Vapor Intrusion At Leaking Underground Storage Tank Sites"

Definition in the UK
Similarly to the US, the UK defines an underground tank as having 10% of its combined potential volume below the ground.

Decommissioning an underground tank in the UK
The requirements set by The Environment Agency for Decommissioning an underground tank apply to all underground storage tanks and not just those used for the storage of fuels. They give extensive guidance in The Blue Book and PETEL 65/34. The Environment Agency states that any tank no longer in use should be immediately decommissioned. This process includes both the closing and removal of a UST system (the tank and any ancillaries connected to it) as a whole and the replacing of individual tanks or lengths of pipe. Regardless of whether the decommissioning of the tank is permanent or temporary; it must be ensured that the tank and all components don't cause pollution. This is true of the removal and of any filling of the tank with inert material.

The Decommissioning of a tank can be via removal from the ground after any volatile gas or liquid has been removed. This is called bottoming and degassing the tank. The other option involved filling the tank with either:

 * A Sand and Cement Slurry
 * Hydrophobic Foam
 * Foamed Concrete

If any plan is made to leave the tank on site, the owner will be responsible for keeping record of:

 * The Tank's Capacity
 * The Product it Contained
 * The Method used to Decommission the tank, if any
 * The Date of the Decommissioning

If any tanks and their pipework have been deemed unsuitable for petroleum spirits then they shouldn't be used for the storage of any hydrocarbon based products without first checking their integrity.

title: Underground storage tank


text:
Talk:Glossary of rowing terms

Image change
Image:Rowing harvard.jpg should be replaced with one (And note that the article is about rowing, not the Harvard team; for those interested the image info should instead include such details. --Jerzy (t) 14:07, 2005 Apr 15 (UTC)
 * without the visually confusing white posts in the immediate background
 * suitable to a caption A racing shell travelling in the same direction as the powerboat.

Image Shouldn't be replaced as the boat is heading the same way, you row facing stern, and the cox, certianly can't stear if he isn't facing forward. You might have been confused by the white posts sir. User: Rob15v

'The inside of a double scull' is a nice pic, but I wish it were MUCH larger. I want to see the toe steering mechanism and can't seem to find reasonable picture anywhere. Here is one that I think is nearly adequate, just to make my point: https://www.vespoli.com/store/images/Complete%20mounted%20on%20footboard.JPG Anybody have a better in-the-boat pic?? Sadsaque (talk) 16:51, 11 August 2016 (UTC)

Quads in the UK
Removed the line about quads usually being coxed except for in elite and international races in the UK - just not true. You can't race a coxed quad anywhere above J15 level! --GoAround 08:01, 13 June 2006 (UTC)
 * Quads in South Australia. In SA under 14's and under 15's row coxed quads. Beginners and 3rd Grade club crews also use these boats. Most clubs will have quad riggers for their flat bottomed coxed fours. Coxless boats are only used for elite crews. Similar systems operate in the other states Ozdaren 12:35, 16 July 2006 (UTC)

Australian terms
In Australia Bowside and Strokeside denotes which side of the boat the oar is located. It is usual practice to say Bowside or Strokeside rower. The terms port and starboard are never used. Gate is now the prefered term for the swivel (rowlock).

After coaching for 15 years I have never heard of the term bisweptual or gumboot seat.

I'm sure my British friends would also agree there is sculling and there is rowing. It seems to be a US invention to calling rowing  sweep. This unfortunately seems to have caught on in Australia. Ozdaren 16:43, 13 July 2006 (UTC)

The Athletes
Ambidextrous - another word is bisweptual. It is used a lot in the UK. It has ~1000 hits on google. —Preceding unsigned comment added by 129.169.174.82 (talk) 09:23, 25 June 2010 (UTC)

 * You'll find that it's a US term, not UK. David Biddulph (talk) 09:49, 25 June 2010 (UTC)

Age Categories
Seeing that someone tried to add the AA category and it was removed I thought I would clarify this portion a bit. I changed the wording of the masters from "and so forth..." to listing all of the categories because the previous wording did not indicate that there was a terminal category (category J, for 80+). There seems to be some confusion about the AA category.... http://www.usrowing.org/Libraries/Events/2011RORnodirectory_1.sflb.ashx> shows AA 21-26 and is supposedly the 2011 rules, however http://www.usrowing.org/Libraries/Referees/2012_Proposed_Rules_Changes_-_Public_Comment.sflb.ashx, which is the proposed changes for the 2012 rules, lists a different version of the rule (under the "current rule" section of the part on 4-104) which does not list the AA category... not sure what's going on there. Ahp378 (talk) 04:24, 16 November 2011 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on Glossary of rowing terms. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added tag to http://www.usrowing.org/Libraries/Referees/2014RORFinalWeb_1.sflb.ashx/2011RORnodirectory_1.sflb.ashx
 * Added archive https://web.archive.org/web/20080502093415/http://www.ballcupregatta.org.uk/competitor.html to http://www.ballcupregatta.org.uk/competitor.html
 * Added archive https://web.archive.org/web/20080911033417/http://www.concept2.co.uk/docs/universities/horr_instructions.doc to http://www.concept2.co.uk/docs/universities/horr_instructions.doc

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 04:28, 31 December 2017 (UTC)

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

title: Talk:Glossary of rowing terms


text: File:Sessions 2000 Jarre Album.jpg

title: File:Sessions 2000 Jarre Album.jpg


text:
Prestbury, Gloucestershire

Prestbury is a village and civil parish in the borough of Cheltenham in Gloucestershire, England. Located on the outskirts of Cheltenham and part of the Tewkesbury parliamentary constituency.

The parish of Prestbury had a population of 6,981 according to the 2011 census.

History
The name of the village means "Priests’ fortified place", from Anglo-Saxon preost and burh, possibly from a fortified manor house belonging to the Bishop of Hereford in the 13th century. The settlement is mentioned as Preosdabyrig in 899-904. Prestbury is listed in the Domesday Book of 1086 as "Presteberie", part of the property of the church of Hereford, with 18 villagers, five smallholders, a priest, a riding man and 11 slaves. By the 13th century it had become Presbery. In 1249 the Bishop of Hereford was granted permission to hold a weekly market along with a three-day annual fair in August.

The village became eclipsed by Cheltenham following the end of the medieval period. The market started to decline in the 15th century and had lapsed completely by the start of the 18th century. In the middle of the 18th century a mineral spring was discovered in the parish, and by 1751 a local landowner, Lord Craven, had a business providing bathing and lodging. However it did not last past the end of the century.

The Prestbury War Memorial is a Cotswold stone gothic revival column with six engraved panels commemorating the villagers who died in the First World War (1914–1918). The memorial was severely damaged in October 2011 in an act of vandalism when the column was toppled to the ground and smashed.

There are claims that Prestbury is the most haunted village in England, and one of the most haunted in Britain. A ghost walk of Prestbury Village featured in episode 59 of the popular "How Haunted? podcast.

Amenities
The village shops include two stores and petrol station with store. There is a public library, three hairdressers, a pharmacy, and a butcher. A brasserie and pub, the King's Arms, was the village's main public house, and it was here that the 19th-century jockey Fred Archer grew up, his father being the landlord of the pub. There are three further village pubs: the Plough, the Beehive and the Royal Oak.

Prestbury Racecourse
The village is home to Prestbury Park, the Cheltenham Racecourse, which holds the Gold Cup race each March. Racehorse trainers Frenchy Nicholson and his son David Nicholson had stables in Prestbury. Notable Nicholson apprentices include Pat Eddery, Walter Swinburn, and Mouse Morris the 2006 Cheltenham Gold Cup winning trainer with the horse War of Attrition.

Governance
Prestbury civil parish has been in the Borough of Cheltenham since 1991; it was in Cheltenham Rural District from 1894 to 1974, and the Borough of Tewkesbury from 1974 to 1991.

The parish is presently split between four wards of the Borough of Cheltenham: Swindon Village, Prestbury, Pittville (a very small part) and Oakley; three electoral divisions of the county of Gloucestershire: St Paul's and Swindon, Pittville and Prestbury, and All Saints and Oakley; and two parliamentary constituencies: Tewkesbury and Cheltenham.

title: Prestbury, Gloucestershire


text:
Talk:Boolean data type

Tableau??
Why is Tableau listed as if it were a programming language? It's a (rather expensive) reporting software package, and while it has a typical eval-based syntax for transforming data from outside data sources, it's not notable as a programming language, certainly no moreso than any of its competitors. Is the goal to list every piece of software that internally has a Boolean type of some sort?

Logic and bits
not (FALSE) 00000000 is (TRUE) 11111111 or -1. Some versions of basic and pascal, treat -1 specifically as being TRUE. Just a thought. Duser404 (talk) 08:20, 4 November 2011 (UTC)

Java Boolean class
In Java there is also a Boolean class, to which one can cast.

Church Booleans
This page should mention something about Church Booleans. Wouter Lievens 11:26, 7 May 2005 (UTC)

Revert over Brainfuck
The last edit was changing the "Brainfuck" references to "Brainf**k" which shouldn't be a change. That is the name of the language so it shouldn't be censored. Also, the anon IP didn't even correctly change the links to which "fuck" is a part of. So I changed it back to what it should be. Chris M. 07:34, 10 January 2006 (UTC)

 * Heres to that, Wikipedia does not censor. Good job--Oxinabox1 08:36, 22 June 2007 (UTC)

 * ???????????????????? (What are you on about?) LOTRrules (talk) 13:49, 17 February 2008 (UTC)
 * Brainfuck. 58.145.148.89 (talk) 10:49, 16 August 2010 (UTC)

Ruby
I don't get the part about Ruby. First the text says Ruby doesn't have a boolean data type, but then it says it has literals true and false. What (dynamic) type are these, then? Strings? Numbers? If they're objects, what class are they? I bet it's "Boolean"... Wouter Lievens 12:30, 11 February 2006 (UTC)

Ruby's true and false literals are objects coming from 2 different classes. This is what can be seen at the console by asking the objects themselves: >> true.class => TrueClass >> false.class => FalseClass Pepe (talk) 02:10, 20 November 2010 (UTC)

Consistent example
The examples should all to the same thing. Rather than Python going on about SPAM and EGGs, and VB talking about the end of the world or what ever.--Oxinabox1 08:39, 22 June 2007 (UTC)
 * The languages don't have consistent handling of boolean values. One example for all would be inappropriate. You should allow scope for each language to show some of its usual ways of using booleans. --Paddy 17:11, 22 June 2007 (UTC)
 * This point should be moot now that the examples have been moved to the respective language Talk pages. --Jorge Stolfi (talk) 00:37, 31 December 2009 (UTC)

Citation tags and OR
I removed all of the citation tags. The adder of these tags states that "assertions about programming languages need references". This is not inline with policy. Policy's test is material that is challenged or likely to be challenged. Thinking that Ada having True and False as "challengable" is very unlikely. The author isn't challenging them to begin with, just that an assert requires a reference (which is not true in terms of policy).

As far as code being considered original research, again, is not inline with policy. Providing simple source code about true/false comparisons is in no way, shape, or form near something like saying vitamin B12 causes AIDS. Code for an established language that demonstrates the syntax and/or semantics of said language, by definition, cannot be original research. Such functionality is inherit to the language. It's like saying that a sample sentence highlighting nouns is original research. Cburnett 01:07, 23 July 2007 (UTC)
 * This point should be moot now that the examples have been moved to the respective language Talk pages. --Jorge Stolfi (talk) 00:38, 31 December 2009 (UTC)

Too Much Sample Code
Just wondering, but are all the code samples really necessary in the article? I think there are probably far too many programming languages out there to represent every single one of them like this. I think the article might read better if it were divided up along the lines of the different models for handling Boolean values, with a single code example for each. Some divisions that come to mind: "Pascal-style" BOOLEAN values that represent True and False; "SQL-style" truth values that can evaluate to True, False, or Unknown; "C-style" 1/0 numeric representation; "XQuery-style" effective Boolean values; etc. Basically I'm proposing rewriting the article to classify the different Boolean data type systems based on their representation of truth values. Right now the article reads as a big list of partial code samples, which I don't think really serves the purpose of explaining Boolean data types. Code samples should supplement the text of the article, not completely replace it. SqlPac (talk) 14:50, 25 March 2008 (UTC)

 * You would need enough categories to represent all the current languages andcategories should represent more than one language. You could have an 'others' category with separate entries for all otherwise un-categorised languages, but you would need to keep this small. --Paddy (talk) 18:09, 25 March 2008 (UTC)

 * There are several ways of representing Boolean values in computer languages, but many languages borrow their implementation strategies from other languages. By reading this article I see no grouping or classification of different Boolean data types in any way. That seems odd considering how closely many of the Boolean data type implementations are to one another. This article could perhaps be more accurately named "Boolean datatype implementation syntax", as that's what it seems to focus on. SqlPac (talk) 19:04, 29 March 2008 (UTC)

Except this article is specifically about the datatype so I think the code that is here is entirely warranted. If this article were about booleans or boolean algebra then I would be more inclined to agree with you.

However, I think a more summarizing section is warranted.

IMO, as a professional programmer, the code speaks more and louder than the accompanying words. Write all the words you want but the actual code speaks the truth about how that language ultimately handles it. Cburnett (talk) 00:10, 26 March 2008 (UTC)

 * IMHO, as a professional programmer, this is a programming "cookbook" article, not an encyclopedic article. Many of the partial code samples will not run without modification, and not all languages mentioned show actual code samples (inconsistency?) At least one of the code samples specifically states that it will not run(!)
 * So the question, I think, is who is this article written for? Is it a code list about programming, by programmers, for programmers?  Or is the objective to explain what a Boolean data type is to a broader audience of people who are not professional programmers?
 * This article appears to be nothing more than a quick reference for people with CS degrees who need a non-comprehensive comparative analysis of Boolean data type syntax in a randomly selected subset of 21 computer languages. If that is the purpose of this article then the cookbook format and randomly selected limited content is wonderful (although it could be improved by applying some level of consistency.)  However, if the article is supposed to explain what the Boolean data type is to non-programmers, then it should be explained in such a way that non-programmers can understand.  Unfortunately that would require possibly replacing a bunch of code snippets with actual text, since the assumption cannot be made that non-programmers necessarily know the syntax and semantics of ALGOL-60 when they visit the page. (I could be wrong - maybe a lot more non-programmers know ALGOL-60 than I am aware of.)
 * BTW, I notice that the following code snippets are not yet included in the article: 6502/6510 Assembler language, Z-80 Assembler Language, x86 Assembler Language, 68000-series Assembler Language, VB.NET, COBOL, Haskell, CLI, Visual J++, SNOBOL, RealBASIC, QuickBASIC, PL/1, PILOT, Modula, Clipper, Mathematica, F#, Eiffel, dBase, Cold Fusion, C--, Ch, SmallTalk, Visual FoxPro, X10, ... . I'll start adding these to bring the article closer to completion, but someone else will need to address the others here: List of programming languages.  I notice that the Wikipedia list of programming languages is not complete either, so we're going to have to get together a list of languages that aren't listed on Wikipedia. SqlPac (talk) 19:04, 29 March 2008 (UTC)

 * Can the article be improved? Absolutely.  Should the code be removed?  Absolutely not.  My interpretation of your original post is more of the latter: discuss true and false as generally used and that's it.  I think every language should be discussed so don't fall into the trap that so many people do that the current state of an article indicates some sort of consensus that it's "done", so while there are 21 languages here it doesn't mean there's some conspiracy to exclude all the others.

 * There are already dicussions of "true" and "false" on Wikipedia Boolean algebra (logic), so it would be pointless to write another article rehashing it again. I don't believe the "list of code snippets" is done, as there are 100's of languages that have been left out. As I said, this article currently consists of a "programming cookbook" style of inconsistent code snippets that reflect an apparently randomly selected tiny sampling of possible programming languages.

 * This article is written for "everyone". Like every other article it should be descriptive for the laymen but also informative to the computer scientist because, by definition, this is a technical article.  I think a summary section is entirely warranted to discuss the generalities because while true/false is generally the same in the various language they do treat booleans quite differently.  For example, C will convert integers to true/false implicitly but C# will refuse to implicitly cast it, and all the while PHP will implicitly convert various strings as true/false.

 * This article is not written for "everyone". It's written in a form that would be useful to, as was pointed out, "professional programmers" who need a quick comparative analysis of syntax for a completely random, and tiny, selection of languages.  How many non-programmers really need that?

 * BTW, your comparison of C (which does not have a Boolean data type) with C# (which does have a Boolean data type) is a comparison of two different systems of representing Boolean values. The Boolean data type in VB 6, QuickBASIC, GW-BASIC, etc., is closely aligned with the C implementation which uses numbers to represent true/false; while the C# implementation is more closely aligned to C++ and Java implementations in that they support native Boolean data types that hold true/false values.  When you compare apples with apples you start seeing the similarities.  Why separate code samples for every single language in existence, especially when many languages share similar implementations?  Is the sentence "____ does not allow implicit casting of boolean data type to ____" really justification to dedicate a whole section to a specific language?

 * How about the PL/I type BIT(1) which can have only two values, but they are '1'B and '0'B instead of TRUE and FALSE? Does that count as a boolean data type? Gah4 (talk) 21:24, 27 September 2011 (UTC)

 * I think the C section covers its boolean datatype fairly well and shows various ways you can achieve a boolean type without actually having one. The section on ML, however, is too much code because it doesn't have much commentary but I see this as a reason to add prose not remove code.  I see it as "too little prose" rather than "too much code".  Cburnett (talk) 23:52, 29 March 2008 (UTC)

 * I see it as far too much code. In .NET framework languages, for instance, the Boolean data type works the same across the board.  Do you really need separate code samples for C#, VB.NET, C++.NET (CLI), Delphi.NET, and every other CLI language?  Do you really need to clog up an article with code samples for every single language in existence, when many languages handle Boolean data types in similar fashion to one another?  This is going to be a very, very, very long article by the time you include code snippets for every language in existence; even if the code snippets are partials that won't run anyway, full of "...".  It makes more sense to me to describe the common implementations of languages and classify the hundreds of available languages according to their logic system implementations for purposes of this article.  Personally I would find that a lot more useful than an article with hundreds of partial code samples that won't run without modification anyway.

 * I suggest recommending the article for peer review to get others' feedback on it. Let others, particularly non-CS-degree holding people decide if adding code samples for every language in existence is the best way to go with this article. As I said, I will be happy to add a dozen or so code samples myself to help bring the article a small step closer to conclusion, but there are still hundreds of languages that need to be addressed.  Is 200+ code samples too much for one article about the Boolean data type?  Will it be useful to the person without a CS degree?  Is the person visiting this page really coming here for a comparative analysis and survey of syntax of Boolean data type implementations in every programming language in the world? SqlPac (talk) 00:54, 30 March 2008 (UTC)
 * Yes, there are far too many code samples. Almost all of them are unreferenced, too. It's some sort of original research programming contest! -- Mikeblas (talk) 01:11, 30 March 2008 (UTC)

 * BTW I'm not at all against code samples, I just don't see the point of superfluous, inconsistent, and non-working code samples. SqlPac (talk) 01:14, 30 March 2008 (UTC)
 * This section should be moot now that the examples have been moved to the respective language Talk pages. --Jorge Stolfi (talk) 00:38, 31 December 2009 (UTC)

Wordgroup for boolean prefix
Usually they name boolean variables something like "isEnabled", "hasItem", "canHandle", "shouldDelete" etc. What is the wordgroup called for the words "is", "has", "can", "should" etc.? The closest I found was Copula, but I doesn't seem to fit every case. -- 88.117.79.142 (talk) 21:48, 28 July 2008 (UTC)

Who are they? It's a common convention, but it's not universal, and it's probably absent in some cultures. Personally (I have a C++ background) I prefer "enabled" to "isEnabled", "!empty" to "hasItem" and, well, the others do not make sense out of context. JöG (talk) 21:57, 9 June 2009 (UTC)

Enum example - can this work?
typedef enum { FALSE, TRUE } boolean; ... boolean b; The following typical preprocessor macros are also often used.

 * 1) define FALSE 0
 * 2) define TRUE 1

Well, the article says *ALSO* often used. However, the enum example won't work before FALSE and TRUE are #defined. Hence this is not optional, but mandatory! [edit] On gcc, you need: typedef enum { false, true } boolean; Note that CAPITALIZING the "false" and "true" will result in errors! (just checked!) -andy 92.230.16.89 (talk) 21:43, 5 November 2008 (UTC)
 * The only way that should cause an error is if FALSE and TRUE were #defined or declared before the enum declaration. For example, some #included header might do that. — DAGwyn 158.12.36.83 (talk) 23:26, 20 June 2011 (UTC)
 * Pascal has almost exactly that. boolean is, eseentially typedef {false, true} bool. Pascal is better in the sense that it is undefined behaviour to try assinging any other value.

19:40, 24 February 2009 (UTC) —Preceding unsigned comment added by SimonTrew (talk • contribs)

What about _Bool in C99?
There is also a built-in (in contrast to the  in  ) boolean type called. Anyone who knows more about this? Rndusr (talk) 08:35, 6 February 2009 (UTC)
 * Actually, the  in   is a #define for  . Not much more to say about it really, but I added the info to the C99 chapter. decltype 09:43, 6 February 2009 (UTC)

 * Bool is a proper first-class datatype now (though implicitly converted to int). I don't have the refs with me, they are at work

SimonTrew (talk) 19:38, 24 February 2009 (UTC)

 * (not ) is a standard (unsigned) integer type in C99, distinct from other types, specified to have a width of at least 1 bit.  It is intended to be used only via   from  .  Conversion to and from type   involve the value of the lowest bit in the representation of , e.g. converting from type   produces 1 if the operand was nonzero and 0 if the operand was zero.  Relational expressions still have type  . — DAGwyn 158.12.36.83 (talk) 23:34, 20 June 2011 (UTC)

Caps
This is probably an old chestnut but should it be Boolean or boolean? I don't mind either but it is inconsistent through the article.

SimonTrew (talk) 19:37, 24 February 2009 (UTC)
 * The abstract data type (not specific to any programming language) should be "a Boolean data type" since that is merely the English word. The name of the data type in specific languages may be,  ,  ,  ,  ,  ,  , ... and case may or may not matter.  All the best,--Jorge Stolfi (talk) 00:44, 31 December 2009 (UTC)

fact tag in C regarding FALSE and TRUE
It is true that the boolean operators ==, !=, >=, <= all return either 1 or 0. But the macros (or enum values)  and   are entirely implementation-dependent, and need not be defined at all. Assuming that the rules for language extensions are similar to those of C++, a program such as

should not compile without a diagnostic message, because  is undefined, or defined as a compiler extension. Either way, the return value of the resulting program is not mandated by the standard. decltype (talk) 02:18, 19 April 2009 (UTC)
 * The relevant part in the text seems to talk about user-defined (not implementation-defined) constants "TRUE" and "FALSE", for example, those defined by "enum { FALSE, TRUE }" or a "#define TRUE 1". In both cases, TRUE will be equal to 1 and, e.g., "(a != b) == TRUE" should work as expected; there is nothing implementation-defined here. I can see the point the text is trying to make, but as it stands, I find it misleading. — Miym (talk) 09:39, 19 April 2009 (UTC)
 * Good point. I have tried to tweak the text a little. I would provide a cite that comparing against TRUE/FALSE is discouraged in C, but I couldn't find one. decltype (talk) 15:32, 19 April 2009 (UTC)

Do you really need a citation for that? When (in a world where TRUE is defined or enum:ed to 1) you write if(foo==TRUE) you are introducing the idea that all values except 1 (0, 2, 3, ...) are false. And then you are in conflict with the language, and quite likely with the guy who wrote foo. One good source is the C FAQ section 9.2. JöG (talk) 20:38, 9 June 2009 (UTC)

Boolean types in Algol 68
There used to be an "Algol 68" section with the following contents:
 * An actual extract from the ALGOL 68 language specification (page 177) where the Boolean operators are defined:

 * 10.2.2. Operations on Boolean Operands
 * op ∨ = (bool a, b) bool:( a | true | b );
 * op ∧ = (bool a, b) bool: ( a | b | false );
 * op ¬ = (bool a) bool: ( a | false | true );
 * op = = (bool a, b) bool:( a∧b ) ∨ ( ¬b∧¬a );
 * op ≠ = (bool a, b) bool: ¬(a=b);
 * op abs = (bool a)int: ( a | 1 | 0 );

Methinks that the above quote from the Algol 68 manual is too cryptic and of little value to the reader; so I have reduced that section to a short mention that Algol 68 had a bool data type pretty much like Algol 60's Boolean. OK? --Jorge Stolfi (talk) 01:13, 21 June 2009 (UTC)

Restructuring proposal: Move examples to the language articles
Would anyone have objections to me changing the article into a Programming Language heading and a Mathematical Theory heading? It seems sort of wrong having lambda calculus sitting next to more practical languages, but on the other hand lambda calculus represents an abstracted PL. --Sam Pointon 18:53, 16 December 2005 (UTC)
 * Alternatively, instead of listing every single language that has a boolean type, a listing of the general systems of boolean representation in use, eg:
 * No special boolean datatypes, single false value: C89, Lisp etc.
 * No special boolean datatypes, multiple false values: Python (multiple categories), Perl, etc.
 * Boolean datatypes, but which only represent 0 and 1: Python (multiple categories), C99, C++, etc.
 * Specialised boolean datatypes, unuseable for other purposes: Java, Smalltalk (I think), etc.
 * --Sam Pointon 19:10, 16 December 2005 (UTC)
 * Hear,hear! Indeed all the good arguments in the section Too Much Sample Code now seem to be moot.  The goal of giving a minimally accurate description of the Boolean data types and operations for every important language is neither viable nor desirable.  Those sections should be all removed from this article and merged into the respective language articles, leaving here only a very succint survey (as in Sam Pointon's suggestion above).  At most, there may be a table with one language per line, listing only the most notable feature of its Boolean types (ditto). --Jorge Stolfi (talk) 01:33, 21 June 2009 (UTC)
 * I have added a merge-to tag to the examples section. If no one objects, I will try to moev each example to the corresponding language article. [unsigned comment by Jorge Stolfi
 * Since there were no objections, I started to move the section as announced above. The subsections have all been copied verbatim to the Talk: pages of the corresponding languages (Talk:C99, Talk:Ruby, Talk:C Sharp, Talk:Lua, etc.)  I suppose that the "curators" of those pages will better know what to do with that material.  (Some languages have extensive syntax pages, other have wikibooks, etc.) Sorry for the inconvenience and for removing so much hard-worked material, but that section, although still incomplete and uneven, was already far too big for one article.  Besides, almost all of the code exmples were largely lost on readers who did not know the corresponding languages.  All the best, --Jorge Stolfi (talk) 00:32, 31 December 2009 (UTC)

Removed LISP example
This example was removed from the History section: It is here in case it may be useful somewhere, someday. --Jorge Stolfi (talk) 22:37, 21 June 2009 (UTC)
 * For example,
 * could be written in C-like syntax
 * could be written in C-like syntax

C section still misleading
The section on C is, again, misleading. It is true that "if" statements and boolean operators such as &&, ||, etc., interpret zero as false and non-zero as true. However, operators such as >, ==, !=, etc., return only values 0 (for false) or 1 (for true). That's how it is both in C90 and in C99. — Miym (talk) 19:41, 28 June 2009 (UTC)
 * Please check whether the description which remained in the "History" section is nnow accurate. All the best, --Jorge Stolfi (talk) 05:57, 31 December 2009 (UTC)
 * Thanks for the edits, overall the article looks much better than it used to be! Regarding this detail, I think it's still slightly inaccurate. I'm not sure how to rephrase it better, but the basic idea should be this:
 * Comparison operators ('>', '==', etc.) and logical operators ('&&', '||', '!', etc.) return a signed integer (int) result, either 0 (for false) or 1 (for true).
 * Logical operators ('&&', '||', '!', etc.) and condition-testing statements ('if', 'while', etc.) interpret a scalar value that is equal to 0 as false and everything else as true.
 * In C99, the _Bool type is not a synonym of int. It is a special type that can only store values 0 and 1 (for example, after "int x = 2; _Bool y = x;" the value of y will be 1, not 2). However, what I said above still holds in C99, too: comparison operators return ints (not _Bools) and condition-testing statements accept any scalar values (including ints, floats, _Bools, etc.).
 * — Miym (talk) 11:27, 31 December 2009 (UTC)

Classification of Lua
I am not sure about how Lua fits in the taxonomy given in the "History" section, so I left it out for now. Here is part of what the article said about it:
 * Lua as of version 5.0. defines a  type which can be either   or  . The special value   (of type  ) also evaluates to false in logical expressions. The logical operators   and   return one of their arguments as the result instead of the value   or.

Help will be appreciated. --Jorge Stolfi (talk) 05:56, 31 December 2009 (UTC)

Perl and AWK
There are a couple issues with this part:

 * 1) The first sentence seems to imply that AWK and Perl have a separate Boolean data type, whereas they do not.
 * 2) While C++ predates Perl, it postdates AWK.

I suggest simply dropping the second sentence. — Preceding unsigned comment added by Nathanweeks (talk • contribs) 02:20, 12 September 2012 (UTC)

Removal of Next Generation Shell
A recent edit removed Next Generation Shell due to lack of sources and proof of notability. Should it have been replaced by a section on PowerShell?

title: Talk:Boolean data type


text:
Mississippi Highway 182

Mississippi Highway 182 (MS 182) designates the old two-lane highway for U.S. Route 82 (US 82) where the current US 82 occupies a new right-of-way. Some of the towns with a segment of MS 182 are Winona, Kilmichael, Eupora, Mayhew, Starkville, and Columbus.

Winona
MS 182 begins at an intersection with US 82 in the western part of Winona in Montgomery County. From here, the highway heads east along two-lane undivided Middleton Road, passing through wooded areas of homes. MS 182 comes to its eastern terminus at an intersection with US 51.

Kilmichael
MS 182 begins at a junction with US 82 northwest of Kilmichael in Montgomery County, heading southeast on a two-lane undivided road through woodedland. The road enters Kilmichael and becomes North Rutherford Drive, passing through wooded areas with homes. The highway intersects the southern terminus of MS 745 near the center of town and continues past more residences on South Rutherford Drive. MS 182 comes to an intersection with the northern termini of both MS 413 and MS 745 and turns to the east. The highway runs through a mix of fields, trees, and homes before it reaches its eastern terminus at US 82 east of Kilmichael.

Eupora
MS 182 begins at an intersection with US 82 west of Eupora in Webster County, heading northeast as a two-lane undivided road. The road passes through a mix of fields and woods with some homes before it curves east and enters Eupora. The highway becomes West Roane Avenue and runs through residential areas. MS 182 heads into the commercial downtown of Eupora, where it becomes East Roane Avenue and crosses MS 9. Past this intersection, the road continues past businesses a short distance to the north of the Columbus and Greenville Railway before it leaves Eupora. The highway becomes unnamed and runs through wooded areas with some fields and homes, curving northeast away from the railroad tracks. MS 182 comes to its eastern end at another intersection with US 82.

Starkville-Mayhew and western Columbus
MS 182 begins at an intersection with US 82 west of Starkville in Oktibbeha County, heading southeast as a two-lane undivided road. The highway runs through forested areas with some fields and homes, passing through the community of Adaton. The road continues through rural areas and curves east. MS 182 enters Starkville and comes to an interchange with MS 25. At this interchange, the highway becomes a four-lane road called Dr. Martin Luther King, Jr. Drive West and passes commercial development before it narrows back to two lanes and runs through wooded areas with homes and businesses. The road continues east through more commercial areas as it passes to the north of downtown Starkville, with the name changing to Dr. Martin Luther King, Jr. Drive East at the Dr. Douglas L. Conner Drive intersection. MS 182 gains a center left-turn lane and intersects the southern terminus of MS 389 a short distance later. The highway passes more businesses and comes to a bridge over a Kansas City Southern Railway line. MS 182 widens into a four-lane divided highway and comes to an interchange with MS 12 on the eastern border of Starkville. After this, the road passes through the northern portion of the Mississippi State University campus.

MS 182 becomes an unnamed divided highway and runs between fields to the north and residential and commercial development to the south of the road. The highway comes to an interchange with the US 82/MS 12/MS 25 freeway in Clayton Village, after which it narrows back into a two-lane undivided road that runs through rural land with some commercial development. The road passes to the south of the Mississippi State University Golf Course before it crosses under US 82/MS 12/MS 25 without an interchange. MS 182 runs through a mix of farm fields and woods with some homes as it heads into Lowndes County. The highway becomes South Frontage Road and reaches an interchange with US 45 Alt. Following this, the road continues through rural land before it reaches the community of Mayhew, where it heads to the north of the East Mississippi Community College Golden Triangle Campus and passes under a Kansas City Southern Railway line. MS 182 runs through woods before continuing straight through farmland. Before the road reaches the roadbed of the US 82/MS 12 freeway, the MS 182 designation formally ends with the roadbed continuing only as Frontage Road.

After about 4+1/2 mi of parallelling the freeway, the MS 182 resumes as a two-lane road continues east to an intersection with US 45. Past this intersection, the road becomes Old Highway 82 West and runs through wooded areas with some fields. MS 182 comes to its terminus just west of the Tennessee–Tombigbee Waterway to the west of Columbus, where the road turns south and becomes Old Macon Road.

Columbus-Alabama
MS 182 begins at a dead end along the western shore of a large island along the Tennessee–Tombigbee Waterway in Columbus, Lowndes County, heading east along two-lane undivided Island Road. The highway passes homes and businesses, turning northeast and passing over the eastern branch of the Tennessee–Tombigbee Waterway. After this bridge, MS 182 comes to an intersection with MS 69, at which point the highway turns southeast to form a concurrency with MS 69 along four-lane divided Main Street. The road soon curves east and heads into the commercial downtown of Columbus. The highway leaves the downtown area and continues past businesses and some homes, becoming a five-lane road with a center left-turn lane and crossing a Kansas City Southern Railway line. MS 69/MS 182 curves northeast, narrowing to three lanes, before turning back east and crossing an Alabama and Gulf Coast Railway line. The roadway continues through commercial areas and passes to the south of a park, becoming a four-lane undivided road, before crossing Luxapallila Creek. MS 69 splits from MS 182 by heading to the south, while MS 182 continues east along Alabama Street, a three-lane road with a center left-turn lane, past businesses along with a few residences. Farther east, the highway leaves Columbus and becomes a two-lane undivided, unnamed road that runs through woodland with some fields and development. The road runs near residential neighborhoods before it intersects Lee Stokes Road, which heads north to an interchange with US 82. MS 182 continues east to its terminus at the Alabama border, where the road continues into that state as CR-30 in Pickens County.

title: Mississippi Highway 182


text:
Mississippi Highway 69

Mississippi Highway 69 (MS 69) is a state highway in eastern Mississippi. The route starts at the Alabama state line, and travels northwestward to Columbus. MS 69 then goes through downtown Columbus, and ends at U.S. Route 45 (US 45) and US 82 in the west side of the town. Before the road was designated as MS 69 in 1941, it was a gravel road from Columbus to the state line. The road was paved in asphalt in 1953. In 1992, US 82 was realigned, and MS 69 was extended through Columbus to its current northern terminus.

Route description
MS 69 starts at the Alabama state line, where Alabama State Route 14 ends. The route turns northwest at Spurlock Road. It travels through the forest, intersecting Weaver Road and Halbert Road. MS 69 moves westward for a short period between Concord Road and East Minnie Vaughn Road. The road then curves slowly towards Columbus, as small streets begin to appear. At Pickensville Road, MS 69 travels north into Columbus, and intersects Fabritek Drive, the entrance to Columbus-Lowndes County Airport. At Yorkville Road, the road meets MS 795's eastern terminus. It soon crosses over the McCrary Vernon Creek and the Alabama Southern Railroad. At MS 182, MS 69 becomes concurrent with it and travels westward. The road soon crosses over Luxapalila Creek and enters downtown Columbus. MS 69 and MS 182 changes into a divided highway at Thirteenth Street. The street then intersects Fifth Street, which becomes US 45 past US 82. MS 182 continues westward on Island Road, while MS 69 travels northwestward. The route ends at US 45 and US 82 at a diamond interchange. The road continues to East Plymouth Road, where it ends at a three-way junction.

All of MS 69 is located in Lowndes County. The route is legally defined in Mississippi Code § 65-3-3, and all of it is maintained by the Mississippi Department of Transportation (MDOT).

History
A gravel road from Columbus to the Mississippi–Alabama state line has existed since 1928, and it was designated as MS 69 by 1941. A $296,187.71 contract awarded by the Mississippi State Highway Commission in 1951 was used to grade the road, add drainage, culverts, and bridges to the route. The road was paved with asphalt by 1953, after being proposed four years earlier by the city of Columbus' Chamber of Commerce. The highway caught on fire in 1957, after a wagon carrying coal tar spilled its contents, destroying multiple telephone lines. In 1958, the northern terminus was rerouted out of downtown Columbus, to east of US 82 and MS 50's intersection. In 1992, US 82 was realigned to the bypass around Columbus, and MS 69 was extended through Columbus to a diamond interchange in the western part of the town.

title: Mississippi Highway 69


text:
Mississippi Highway 50

Mississippi Highway 50 (MS 50) is a state highway in Mississippi. It generally follows an east/west track for 60 mi and runs from MS 9 in Walthall, Mississippi, east to the Alabama state line east of Columbus. MS 50 serves the following Mississippi counties: Lowndes, Clay, and Webster.

Route description
MS 50 begins in the North Central Hills region (part of the Appalachian Foothills) in Webster County at an intersection with MS 9 in the village of Walthall. It heads east as a two-lane highway through downtown, where it has an intersection with MS 784 (Main Street), before leaving Walthall and continuing east through rural areas for a few miles to an intersection with Clarkson Road and N Sappa Road, where state maintenance ends and the road winds its way east through remote wooded areas as Old Highway 50 and Avent Road (parts of which are unpaved dirt road). The county road passes through the community of Clarkson, where it briefly turns right onto Clarkson road, before turning left onto Abbott Road for half a mile, and then turning left onto Cole Road and leaving the community. Cole Road passes through a mix of farmland and woodlands for the next several miles, where it becomes paved as well as becoming Jackson Road, before coming to an intersection with Old Cumberland Road (CR 167). Here MS 50, as well as state maintenance, restarts and heads along Old Cumberland Road to cross under the Natchez Trace Parkway and enter the community of Cumberland. MS 50 passes straight down the center of the community, where it has an intersection with MS 765 (Natchez Trace Road, a connector to the parkway), before leaving Cumberland and coming to an intersection with MS 15. MS 50 becomes concurrent with MS 15 and they head south through woodlands for several miles before MS 50 splits off and continues east to cross into Clay County.

MS 50 now enters the Golden Triangle region and it passes through the community of Pheba, where it has an intersection with MS 389. The highway travels through the community of Cedar Bluff before having intersections with both MS 46 and MS 47 and entering the West Point city limits. MS 50 passes through some neighborhoods before having an intersection with US 45 Alternate/MS 25 and passing straight through downtown along Main Street. The highway now passes through more neighborhoods before leaving West Point and traveling east-southeast through farmland for several miles to the community of Waverly, where it crosses a bridge over the Tombigbee River (Tennessee Tombigbee Waterway) into Lowndes County.

MS 50 travels through wooded areas for several miles to become concurrent with MS 373 before coming to an intersection US 45, where MS 373 ends and MS 50 turns south along US 45. The highway enters the Columbus city limits as an undivided four-lane and soon passes through a long major business district for a few miles to come to an interchange with US 82 (unsigned MS 12) just north of downtown, with US 45 heading west along US 82, MS 50 heading east along US 82, and the road continuing into downtown as MS 69 (N 5th Street). US 82/MS 12/MS 50 head east along a four-lane freeway that bypasses the entire downtown area on its north side, having interchanges with 18th Avenue N and Military Road (as well as crossing Luxapallila Creek). MS 12/MS 50 split off from US 82 at an interchange with Tuscaloosa Road, heading east as a four-lane boulevard through a business district for not even a mile to an intersection where MS 12 splits off and heads north. MS 50 now narrows to two-lanes and leaves Columbus, traveling through farmland for several miles to come to the Alabama state line southeast of Steens, with the road continuing into Alabama as State Route 96 (SR 96).

History
MS 50 was originally designated in 1932 as Mississippi Highway 10 (MS 10). It was redesignated in 1960 as MS 50 to eliminate confusion with then newly constructed I-10.

title: Mississippi Highway 50


text:
Sock puppet account

A sock puppet is a false online identity used for deceptive purposes. The term originally referred to a hand puppet made from a sock. Sock puppets include online identities created to praise, defend, or support a person or organization, to manipulate public opinion, or to circumvent restrictions such as viewing a social media account that a user is blocked from. Sock puppets are unwelcome in many online communities and forums.

History
The practice of writing pseudonymous self-reviews began before the Internet. Writers Walt Whitman and Anthony Burgess wrote pseudonymous reviews of their own books, as did Benjamin Franklin.

The Oxford English Dictionary defines the term without reference to the internet, as "a person whose actions are controlled by another; a minion" with a 2000 citation from U.S. News & World Report.

Wikipedia has had a long history of problems with sockpuppetry. On October 21, 2013, the Wikimedia Foundation (WMF) condemned paid advocacy sockpuppeting on Wikipedia and, two days later on October 23, specifically banned Wiki-PR editing of Wikipedia. In August and September 2015, the WMF uncovered another group of sockpuppets known as Orangemoody.

Block evasion
One reason for sockpuppeting is to circumvent a block, ban, or other form of sanction imposed on the person's original account.

Ballot stuffing
Sockpuppets may be created during an online poll to increase the puppeteer's votes. A related usage is the creation of multiple identities, each supporting the puppeteer's views in an argument, attempting to position the puppeteer as representing majority opinion and sideline opposition voices. In the abstract theory of social networks and reputation systems, this is known as a Sybil attack.

A sockpuppet-like use of deceptive fake identities is used in stealth marketing. The stealth marketer creates one or more pseudonymous accounts, each claiming to be a different enthusiastic supporter of the sponsor's product, book or ideology.

Strawman sockpuppet
A strawman sockpuppet (sometimes abbreviated as strawpuppet) is a false flag pseudonym created to make a particular point of view look foolish or unwholesome in order to generate negative sentiment against it. Strawman sockpuppets typically behave in an unintelligent, uninformed, or bigoted manner, advancing "straw man" arguments that their puppeteers can easily refute. The intended effect is to discredit more rational arguments made for the same position. Such sockpuppets behave in a similar manner to Internet trolls.

A particular case is the concern troll, a false flag pseudonym created by a user whose actual point of view is opposed to that of the sockpuppet. The concern troll posts in web forums devoted to its declared point of view and attempts to sway the group's actions or opinions while claiming to share their goals, but with professed "concerns". The goal is to sow fear, uncertainty and doubt (FUD) within the group.

Meatpuppet
Some sources have used the term meatpuppet as a synonym for sock puppet.

Investigation of sockpuppetry
A number of techniques have been developed to determine whether accounts are sockpuppets, including comparing the IP addresses of suspected sockpuppets and comparative analysis of the writing style of suspected sockpuppets. Using GeoIP it is possible to look up the IP addresses and locate them.

United States v. Drew
In 2006, Missouri resident Lori Drew created a MySpace account purporting to be operated by a fictitious 16-year-old boy named Josh Evans. "Josh Evans" began an online relationship with Megan Meier, a 13-year-old girl who had allegedly been in conflict with Drew's daughter. After "Josh Evans" ended the relationship with Meier, the latter committed suicide.

In 2008, Thomas O'Brien, United States Attorney for the Central District of California, charged Drew, then 49, with four felony counts: one count of conspiracy to violate the Computer Fraud and Abuse Act (CFAA), which prohibits "accessing a computer without authorization via interstate commerce", and three counts of violation of the CFAA, alleging she violated MySpace's terms of service by misrepresenting herself. O'Brien justified his prosecution of the case because MySpace's servers were located in his jurisdiction. The jury convicted Drew of three misdemeanor counts, dismissing one on the grounds prosecutors had failed to demonstrate Drew inflicted emotional distress on Meier.

During sentencing arguments, prosecutors argued for the maximum sentence for the statute: three years in prison and a fine of $300,000. Drew's lawyers argued her use of a false identity did not constitute unauthorized access to MySpace, citing People v. Donell, a 1973 breach of contract dispute, in which a court of appeals ruled "fraudulently induced consent is consent nonetheless." Judge George H. Wu dismissed the charges before sentencing.

People v. Golb
In 2010, 50-year-old lawyer Raphael Golb was convicted on 30 criminal charges, including identity theft, criminal impersonation, and aggravated harassment, for using multiple sockpuppet accounts to attack and impersonate historians he perceived as rivals of his father, Norman Golb. Golb defended his actions as "satirical hoaxes" protected by free-speech rights. He was disbarred and sentenced to six months in prison, but the sentence was reduced to probation on appeal.

New Directions for Young Adults, Inc. v. Davis
In 2014, a Florida state circuit court held that sock puppetry is tortious interference with business relations, and awarded injunctive relief against it during the pendency of litigation. The court found that "the act of falsifying multiple identities" is conduct that should be enjoined. It explained that the conduct was wrongful "not because the statements are false or true, but because the conduct of making up names of persons who do not exist to post fake comments by fake people to support Defendants' position tortiously interferes with Plaintiffs' business" and such "conduct is inherently unfair." The court, therefore, ordered the defendants to "remove or cause to be removed all postings creating the false impression that more [than one] person are commenting on the program th[an] actually exist." The court also found, however, that the comments of the defendants "which do not create a false impression of fake patients or fake employees or fake persons connected to program (those posted under their respective names) are protected by The Constitution of the United States of America, First Amendment."

Business promotion
In 2007, the CEO of Whole Foods, John Mackey, was discovered to have posted as "Rahodeb" on the Yahoo! Finance Message Board, extolling his own company and predicting a dire future for its rival, Wild Oats Markets, while concealing his relationship to both companies. Whole Foods argued that none of Mackey's actions broke the law.

During the 2007 trial of Conrad Black, chief executive of Hollinger International, prosecutors alleged that he had posted messages on a Yahoo! Finance chat room using the name "nspector", attacking short sellers and blaming them for his company's stock performance. Prosecutors provided evidence of these postings in Black's criminal trial, where he was convicted of mail fraud and obstruction. The postings were raised at multiple points in the trial.

Book and film reviews
An amazon.com computer glitch in 2004 revealed the names of many authors who had written pseudonymous reviews of their books. John Rechy, who wrote the best-selling novel City of Night (1963), was among the authors unmasked in this way, and was shown to have written numerous five-star reviews of his own work. In 2010, historian Orlando Figes was found to have written Amazon reviews under the names "orlando-birkbeck" and "historian", praising his own books and criticizing those of historians Rachel Polonsky and Robert Service. The two sued Figes and won monetary damages.

During a panel discussion at a British Crime Writers Festival in 2012, author Stephen Leather admitted using pseudonyms to praise his own books, claiming that "everyone does it". He spoke of building a "network of characters", some operated by his friends, who discussed his books and had conversations with him directly. The same year, after he was pressured by the spy novelist Jeremy Duns on Twitter, who had detected possible indications online, UK crime fiction writer R.J. Ellory admitted having used a pseudonymous account name to write a positive review for each of his own novels, and additionally a negative review for two other authors.

David Manning was a fictitious film critic, created by a marketing executive working for Sony Corporation to give consistently good reviews for releases from Sony subsidiary Columbia Pictures, which could then be quoted in promotional material.

Blog commentary
American reporter Michael Hiltzik was temporarily suspended from posting to his blog, "The Golden State", on the Los Angeles Times website after he admitted "posting there, as well as on other sites, under false names." He used the pseudonyms to attack conservatives such as Hugh Hewitt and L.A. prosecutor Patrick Frey—who eventually exposed him. Hiltzik's blog at the LA Times was the newspaper's first blog. While suspended from blogging, Hiltzik continued to write regularly for the newspaper.

Lee Siegel, a writer for The New Republic magazine, was suspended for defending his articles and blog comments under the username "Sprezzatura". In one such comment, "Sprezzatura" defended Siegel's bad reviews of Jon Stewart: "Siegel is brave, brilliant and wittier than Stewart will ever be."

Politically oriented
In late November 2020, TYT Network reported an example of a white male Republican Trump voter having a sockpuppet Twitter account presented as that of a black gay man, criticizing Biden and praising Trump while systematically emphasizing his race and sexual orientation. Additionally, in October 2020, Clemson University social media researcher identified "more than two dozen of Twitter accounts claiming to be black Trump supporters who gained hundreds of thousands of likes and retweets in a span of just a few days, sparking major doubts about their identities," many using photos of black men from news reports or stock images "including one in which the text 'black man photo' was still watermarked on the image".

Government sockpuppetry
As an example of state-sponsored Internet sockpuppetry, in 2011, a US company called Ntrepid was awarded a $2.76 million contract from U.S. Central Command for "online persona management" operations to create "fake online personas to influence net conversations and spread U.S. propaganda" in Arabic, Persian, Urdu and Pashto as part of Operation Earnest Voice.

On September 11, 2014, a number of sockpuppet accounts reported an explosion at a chemical plant in Louisiana. The reports came on a range of media, including Twitter and YouTube, but U.S. authorities claimed the entire event to be a hoax. The information was determined by many to have originated with a Russian government-sponsored sockpuppet management office in Saint Petersburg, called the Internet Research Agency. Russia was again implicated by the U.S. intelligence community in 2016 for hiring trolls in the 2016 United States presidential election.

The Institute of Economic Affairs claimed in a 2012 paper that the United Kingdom government and the European Union fund charities that campaign and lobby for causes the government supports. In one example, 73% of responses to a government consultation were the direct result of campaigns by alleged "sockpuppet" organizations.

title: Sock puppet account


text:
Talk:Jacob van Artevelde

[Untitled]
Category:Belgian politicians? Seems a bit anachronistic... / Uppland 14:18, 15 Apr 2005 (UTC)

title: Talk:Jacob van Artevelde


text: User talk:81.23.201.170

title: User talk:81.23.201.170


text:
Springfield Presbytery

The Springfield Presbytery was an independent presbytery that became one of the earliest expressions of the Stone-Campbell Movement. It was composed of Presbyterian ministers who withdrew from the jurisdiction of the Kentucky Synod of the Presbyterian Church in the United States of America on September 10, 1803. It dissolved itself on June 28, 1804, with the publication of a document titled the Last Will and Testament of The Springfield Presbytery, marking the birth of the Christian Church of the West.

History
The immediate cause of withdrawal by the ministers was that the Synod of Kentucky had censured the Washington Presbytery for the following:
 * appointing Richard McNemar, after having previously examined his doctrine and condemning it as "dangerous to the souls of men, and hostile to the interests of all religion;"
 * refusing a petition to examine the doctrine of a second minister, John Thompson; and
 * refusing to reexamine the doctrine of McNemar. Both ministers had expressed views at odds with the Westminster Confession. These two ministers and three others (Robert Marshall, John Dunlavy, and Barton W. Stone) protested the proceedings of the Synod and withdrew from its jurisdiction. Their signed protest was dated September 10, 1803.

They gave the following reasons for withdrawing from the jurisdiction of the Synod:
 * belief that the resolution condemning McNemar's teachings (which they all shared) gave "a distorted and false representation of Mr. McNemar's sentiments" and was "calculated to prevent the influence of truth of the most interesting nature";
 * assertion of the privilege of interpreting scripture independently of the Presbyterian Confession of Faith, appealing to the section in that confession that says, "the Supreme Judge, by which all controversies of religion are to be determined, and all decrees of councils, opinions of ancient writers, doctrines of men and private spirits, are to be examined, and in whose sentence we are to rest, can be no other than the Holy Spirit speaking in the Scriptures";
 * argued that some of the doctrines of grace were "in a measure darkened by some expressions in the Confession of Faith [regarding the doctrine of predestination], which are used as a means of strengthening sinners in their unbelief, and subjecting many of the pious to a spirit of bondage," and said that when they tried to address those difficulties, they were accused of departing from the faith.

Based on those reasons, the ministers said that they chose to withdraw from the jurisdiction of the Kentucky Synod rather than be prosecuted under the authority of the Confession of Faith, which they could not acknowledge. But, they said they did not desire to break from communion with the members of the Synod.

They formed the Springfield Presbytery two days later. The Springfield Presbytery was a loose association of the dissenting ministers and their congregations. The Presbytery ordained a sixth minister, David Purviance, who joined it after the West Lexington Presbytery of Kentucky had refused to ordain him.

On January 31, 1804, the several ministers published a 141-page defense of their actions, in which they opposed the use of creeds to determine who is a Christian. The defense was entitled ''An Apology for Renouncing the Jurisdiction of the Synod of Kentucky. To Which Is Added a Compendious View of the Gospel and a Few Remarks on the Confession of Faith.  The Apology'' was written by Robert Marshall. It argued that the examination of McNemar in 1802 had been conducted without due process, which would have justified an appeal of the decision to the General Assembly. It went on to argue that they had no reasonable hope of redress within the Presbyterian church as long as "human opinions", rather than scripture, were the standard of orthodoxy.

Stone wrote the Compendious View of the Scripture. Systematically laying out the doctrines which the Washington Presbytry had condemned, he wrote the first theological statement of the Restoration Movement.

Thompson wrote the Remarks on the Confession, arguing that, since creeds served to divide the church, even if a perfect creed could be found, it should be rejected as the standard for Christian fellowship. The unstated implication was that unity was preferable to orthodoxy.

By 1804 the Springfield Presbytery had attracted 15 congregations in Ohio and Kentucky. The leaders of this newer presbytery became concerned by its growth, as they did not want to create a new denomination or "party". Ultimately convinced that their newer Springfield Presbytery was sectarian, the six ministers dissolved it on June 28, 1804. To publicize the dissolution, they signed a document entitled The Last Will and Testament of the Springfield Presbytery.  This tract willed that "this body die, be dissolved, and sink into union with the Body of Christ at large." It expressed the desire for Christian union and identified the Bible as the only standard of Christian faith and practice.

In addition to signing the Last Will and Testament, the ministers agreed to take "no other name than "Christians," on the basis that it was "the name first given by divine authority to the disciples of Christ." Soon, they adopted the name "Christian" to identify their group. Thus, former congregations from the Springfield Presbytery eventually became known as the Christian Church.  It is estimated that the Christian Church numbered about 12,000 by 1830.

The Last Will and Testament

The Last Will and Testament became a founding document of the Restoration Movement. The dissolution of the Springfield Presbytery was in part a symbolic act, based on the principle that gave priority to individual autonomy for local congregations. Such Congregational ideals are still fundamental to the Disciples of Christ and the Churches of Christ, due in no small part to this document. The document titled Last Will and Testament of The Springfield Presbytery was signed by Robert Marshall, John Dunlavy, and Richard McNemar on June 28, 1804, in the presence of B. W. Stone, John Thompson, and David Purviance, who served as witnesses.

title: Springfield Presbytery


text:
Talk:Lampeter Geography School

I disagree that this article should be merged with the University article. The Lampeter school did not have its biggest impact whilst the department was still open in Lampeter, since most of the academics were at the beginning of their careers. It is since the department has closed that it has been recognised how influential it was. As such, the 'Lampeter Geography School' refers more to the Lampeter diaspora than it does to the department as it existed at the university Twrist 14:19, 15 Apr 2005 (UTC)
 * I agree, but this article has got to be hugely expanded to accurately represent the importance of the Lampeter Diaspora 194.80.178.1 14:25, 15 Apr 2005 (UTC)
 * I'm on it ;) Twrist 14:26, 15 Apr 2005 (UTC)

title: Talk:Lampeter Geography School