American Tipping is Rooted in Slavery

5 Feb 2021 Update (nearly 7 years already): the New York Times has published an editorial by Michelle Alexander titled “Tipping Is a Legacy of Slavery: Abolish the racist, sexist subminimum wage now.


There was no tipping in America before Civil War.

It was during the 1920s — the second rise of KKK after Civil War ended — when all anti-tipping laws were repealed in America to make way for white supremacists to promote it as somehow better for someone. Why was the KKK campaigning to legalize tipping?

A labor review of December 1937 asks a very poignant question about why upwardly mobile blacks in Washington (1909), DC (1910), Mississippi (1912), Arkansas (1913) Iowa, South Carolina and Tennessee (1915) as well as several other states would pass anti-tipping laws only to find them repealed a few years later:

In view of the fact that the anti-tipping sentiment was still strong in the early and middle twenties, one may wonder why the anti-tipping laws were repealed.

When they say anti-tipping sentiment was strong, consider that unionized waiters of New York went on strike in 1906 to refuse tips and demand a minimum wage increase from $2.00/day to $2.50.

Source: 1909 Street’s Pandex of the News, p. 316

It would seem the unions were not ordering strikes for higher tips, only for higher wages.

I should probably make a special note here that when Washington DC banned tips in 1910, basically everyone affected was African American. It clearly was about race and livable wages.

What changed in the early 1920s? The KKK returned.

Indeed, this is like asking why the south went to war to preserve slavery in view of the fact that anti-slavery sentiment was strong.

Or perhaps it would be like asking why the KKK pushed so hard for prohibition (encoded criminalization of non-whites) in view of the fact that anti-prohibition (emancipated slaves distilling bourbon) sentiment was still strong.

In other words, anti-tipping laws started in 1909 before the KKK was restarted and all were repealed after. The KKK quickly grew to millions of members under Woodrow Wilson’s administration (1912-1921) and restoring tipping culture was top on their agenda.

One almost could make the argument that anti-tipping laws were a symptom of the changes in America that really inflamed “white insecurity” fears. The late 1890s racist political campaigns took on new urgency to remove anything that could give black Americans fair wages (Update in 2020: “Wilmington’s Lie: The Murderous Coup of 1898 and the Rise of White Supremacy“).

You could say tipping is how racist Americans who lost their Civil War managed to instead legalize their persistent “only white men rule” aims for aristocratic-like power over the now-emancipated black servant class in America.

The abrupt end of slavery in America meant white supremacists shifted tactics to find ways to deny livable wages to non-whites. They also sought to under-fund or block taxation to reduce the social services (education, healthcare) for those they had just denied a livable wage. NPR brings forward several examples of sentiment from the early 1900s after Civil War ended:

…journalist John Speed writing in 1902 said “Negroes take tips, of course, one expects that of them – it is a token of their inferiority. But to give money to a white man was embarrassing to me.” Such was the furor surrounding tipping that, in 1907, Sen. Benjamin Tillman of South Carolina – a virulent segregationist whose bronze statue stands outside the statehouse in Columbia – actually made national headlines for tipping a black porter at an Omaha hotel. The porter, well aware of Tillman’s previous boast that he never “tips a nigger,” told reporters sardonically that he would have the quarter made into a watch charm. “Tillman gives Negro a Tip,” was The New York Times’ headline, under which ran a sympathetic editorial on how travelers were forced “to convert themselves into fountains playing quarters upon the circumambient Africans.”

Thus it was two basic economic tactics meant to undermine black prosperity in America that became the foundation of America’s racist and hateful tipping culture. And the KKK was so successful the practice survives to this day.

Brazil maintained slavery even longer than America. It even convinced American Civil War losers to immigrate so they could continue slavery overtly instead of tipping.

That’s the short version of history. Now for the long form…


Some in America saw the dangers of tipping early and worked to shut-down such anti-democratic culture, arguing correctly it violated core American values. There were numerous anti-tipping laws in the early 1900s. Here you can see some of the views of tipping in America at that time:

“Tipping: An American Social History of Gratuities”, by Kerry Segrave, p. 6

The KKK was reborn in 1915, however, and had massive impact on American culture pushing things like the racist prohibition laws (1920 to 1933). No surprise then, by 1926 the white supremacist lobby had repealed anti-tipping laws.

One of the most powerful arguments, seen here in a 1916 rebuke of Americans worshiping aristocracy, is how tipping culture is so obviously incompatible with democracy.

“The Itching Palm: A Study of the Habit of Tipping in America”, by William R. Scott, 1916

This clear analysis of American “tipping” is confirmed by a Paris Food History blog recollection of where and why tipping culture was invented…French aristocracy and corruption:

These are all examples of an aristocrat giving a gratification to various workers […] It is unlikely on the other hand that diners in taverns and the cheaper cabarets gave tips. This was an obligation for aristocrats – or, probably, those who wanted to emulate them. And it even extended to those in the prison which most often held them: the Bastille. […] Everywhere you eat, submit without a murmur to the tax of the tip. It is illogical, absurd, exorbitant, vexatious […] In 1856, August Luchet described the tronc in which all tips were gathered: “a cylindrical metal safe, split on top.” He also wrote that (not unexpectedly) distribution of the collected tips was not always to the advantage of the servers; some owners found various pretexts for redirecting or appropriating some portion of the funds.

New York, arguably modeled on Paris at its hey-day, has now become the epitome of the “aristocrats in a prison” culture as described above.

This was nicely documented just last year by Lynne Truss as she visited from Europe

…tips are not niceties: give a “thank you” that isn’t green and foldable and you are actively starving someone’s children. This is not only demeaning for everyone; it also makes you feel, basically, that you are being constantly taken…

She’s not wrong. The economics of tipping look to be a disaster for everyone involved. The Economic Policy Institute explains that poverty rates of tipped workers is nearly double other workers and three times more likely to be on food stamps:

Tipped workers — whose wages typically fall in the bottom quartile of all U.S. wage earners, even after accounting for tips — are a growing portion of the U.S. workforce. Employment in the full-service restaurant industry has grown over 85 percent since 1990, while overall private-sector employment grew by only 24 percent. In fact, today more than one in 10 U.S. workers is employed in the leisure and hospitality sector, making labor policies for these industries all the more central to defining typical American work life.

In other words, by tipping, you are pushing less money into a tax pool while at the same time driving the person tipped to need more tax-funded assistance. It’s quite literally a means for aristocrats to appear good in a fleeting personal moment, while actually keeping poor workers in a place they can’t escape.

This shouldn’t be news to anyone. For ten years already we’ve had quantitative data to support what all these arguments above are saying.

The data at this point shows that tipping has become the norm in America as a legalized method to keep non-whites poor in an anti-democratic push for white nationalist aristocracy, and it doesn’t really serve any other purpose.

…98 percent of [21 million Americans eating out] leave a voluntary sum of money (or tip) for the servers who waited on them. These tips, which amount to over $20 billion a year, are an important source of income for the nations’ two million waiters and waitresses. In fact, tips often represent 100 percent of servers’ takehome pay because tax withholding eats-up all of their hourly wages. The income implications of tipping make it a major concern…weak service-tipping relationship, I argued, raises serious questions about the use of tips as a measure of server performance or customer satisfaction as well as the use of tips as incentives to deliver good service….weak relationship between tips and service quality at this level of analysis undermines the use of tips as a measure of customer satisfaction and an incentive to deliver good service.

This also has been described by psychologists in similar terms:

Empirical evidence suggests that tips are hardly affected by service quality…people derive benefits from tipping including impressing others and improving their selfimage as being generous and kind…. Whether the social norm of tipping increases social welfare depends crucially on the question whether tipping increases service quality. Although service quality is generally high, which could lead us to think that tipping is the incentive that causes waiters to provide excellent service, the analysis above shows that the sensitivity of tips to service quality is so small that tipping is not likely to be the reason for the high service quality. Consequently, tipping, at least in restaurants, does not seem to improve social welfare and economic efficiency by improving service quality

Again, just to be clear we’ve seen for over a decade studies have repeatedly proven “tipping was not significantly related to servers’ or third-parties’ evaluations of the service.”

Tipping really should be treated as an insult and disrespect, when you think about what’s going on.

I remember one night on a work trip in Copenhagen I asked a waitress if I could leave a tip and she angrily replied:

I am paid a reasonable salary for my work and I am good at it. I go to school for free and get healthcare for free. This isn’t your corrupt greed-driven American system. Tips are rude.

She was right. I was caught out for being so… American, unintentionally imposing slavery culture.

There’s no actual link for tipping to better service when you look at the data so my tip in her country made no sense because they have no aristocratic aspirations or need to perpetuate an economic disparity. She wasn’t desperate for an aristocrat to keep her afloat. Since she and I were in a balanced professional engagement, an amount already was settled and handing her a few bills was an insulting gesture.

Taking pride in your work and doing a good job don’t actually come from tips, as restaurateurs explain themselves.

In any workplace, everyone is required to perform well, and tips have nothing to do with it.

We see scientists report that tipping in America is racist by design, perpetuating the aristocratic aspirations of pre-Civil War Americans, and does exactly what the KKK had hoped it would.

The data show very clearly that African Americans receive less in tips than whites, and so there is a legal argument to be made that as a protected class, African American servers are getting less for doing the same work. And therefore, the institution of tipping is inherently unfair.

It is inherently unfair because that is what it was always intended to be, if you accept the argument that it was a loophole for perpetuation of white nationalist policy.

What tips have to do with is a Civil War started by white aristocrats to perpetuate and expand human slavery. Despite losing that war, white supremacists have found numerous ways to maintain programs designed to disadvantage non-whites. That is how American tipping is rooted in slavery and should be abolished.

Yet “Unother” heartbleed Perspective (YUhP)

With so many people talking about heartbleed and offering their insights (e.g. excellent posts from Bruce Schneier and Dan Kaminsky) I could not help but add my own. That is not entirely true. I was happy to let others field questions and then reporters contacted me and wanted insights. After I sent my response they said my answers were helpful, so I thought I might as well re-post here.

So this is what I recently sent a reporter:

What is Heartbleed?

Heartbleed is a very small change made to small part of code that is widely used to protect data. You might even say it is a flaw found in the infrastructure that we all rely upon for privacy. It is not an understatement to say it impacts just about everyone who has a password on the Internet. It’s basically like discovering all your conversations for the past two years that you thought were private actually could have been heard by someone without any effort. This is very dangerous and why it had to be fixed immediately. Potential for harm can be huge when trusted systems have been operating with a flaw. It is hard to quantify who really has been impacted, however, because the damage is a leak rather than an outage. We could look for evidence of leaks now, because people trying to take advantage of the leak will leave particular tracks behind, but it is very unlikely tracks will have been preserved for such a long time, since the code change was made. The change unfortunately was not recognized as dangerous until very recently.

How is it related to encryption and the websites I use?

The simple explanation is that encryption was used on websites (as well as many other sites, including email) to protect data. Encryption can prevent someone from seeing your private information. A change in code, known as OpenSSL, used for encryption actually undermined its ability to protect your data. Heartbleed means someone from a remote location can see data that was believed and intended to be private. Your password, for example, would have been seen by someone who knew of this OpenSSL flaw.

If possible, how can I protect myself now that it’s happened?

You can protect yourself going forward with two simple steps. First verify the sites you use have fixed the heartbleed flaw. Often they will push a notice saying they have addressed the problem, or they will post a notice that is easy to find on their site, or you can consult a list of sites that have been tested. Second, change your passwords.

Another way to protect yourself is to get involved in the debate. You could study the political science behind important decisions, such as when and how to trust changes, or the economics of human behavior. You also could study the technical details of the code to join the debate on how best to improve the quality that everyone may rely upon for their most trusted communication.

The reach of this story is amazing to me. It is like information security just became real for every person in every home. I sat on a bench in an airport the other day and listened to everyone around me give their (horribly incorrect) versions of heartbleed. Some thought it was a virus. Some thought it was related to Windows XP. But whatever they said, it was clear they suddenly cared a lot about whether and how they can trust technology.

I was probably too bullish on the traces/trail part of my answer. It is hard to stay high level while still figuring out some of the details underneath. I haven’t yet built a good high-level explanation for why the attack is not detectable by the system itself but that attack traffic has some obvious characteristics that can be captured by the system.

Anyway, this clearly boils down to code review. It is a problem as old as code itself. A luminary in the infosec space recently yelled the following on this topic:

THIS IS CALLED A BOUNDS CHECK. I SAW CODING ERRORS LIKE THIS IN THE 70’S

We know there are people very motivated to pore over every memcpy in an OpenSSL codebase, for example, to look for flaws. Some say the NSA would have found it and used it, but in reality the threat-scape is far larger and the NSA officially has denied awareness.

We also know that finding a really bad bounds check does not necessarily mean any obligation to report it in a “fair” way that minimizes harm, which is a harsh reality that begs the question of human behavior. Before looking to deeply at the technical aspects of the problem, consider Bruce’s perspective:

This may be a massive computer vulnerability, but all of the interesting aspects of it are human.

If you are Bruce, of course you would say that. He finds human aspects interesting, with all due respect, because it is the less familiar angle to him — the focus of his new research. However, most people are unfamiliar with technology, let alone encryption and keys, so the human aspects are the less interesting angle and they want the technical problem explained. XKCD sees this latter demand. That’s why we now have the following beautiful explanation of technical aspects:

heartbleed

With that in mind I still actually agree with Bruce. The industry really needs to dig deep into the following sequence of events related to trusted infrastructure change controls and bug discovery. This is what I’ve gathered so far. We may learn more and revise this in the future, but I hope it helps illustrate the sort of interesting human aspects to sort out:

  1. OpenSSL code that created heartbleed is committed an hour before midnight on New Years Eve 2011
  2. Codenomicon in early 2014 started tested an alpha piece of their Defensics fuzz product called Safeguard — their automated tool in April finds a flaw in the authentication layer of OpenSSL messaging
  3. Flaw is privately communicated by Codenomicon to CERT in Finland
  4. Someone at Google finds the same flaw and notifies OpenSSL
  5. OpenSSL issues a patch and flaw goes public, leaving many scrambling to respond on an immediate basis

One other thought. I alluded to this in my answer to the journalist but I want to make a finer point here. Some are calling this a maximum level danger event. That perspective begs whether data being destroyed, changed or denied could ever been seen as more dangerous. To a cryptography community the 11 out of 10 event may be different to the availability community. That actually seems to be one of the reasons I have seen management allow encryption to fail — availability risks were seen as more dangerous than confidentiality risks when unfortunately there was a trade-off.

Updated to add: Google staff have started to actively dispute claims anyone found the bug earlier than their company did. Microsoft and Facebook offered money to the Google person who proved the bug to them first, but the money was redirected to a charity rather than accepted.

A timeline favoring Google’s interpretation of events, with the vague discovery listed as “March 21 or before,” has been published by a paper in Sydney. Note the author request:

If you have further information or corrections – especially information about what occurred prior to March 21 at Google – please email the author…

This makes it sound like Google needs help to recall events prior to March 21, or doesn’t want to open up. Codenomicon claims were that it had been testing months prior to discovery. In any case, everything seems to initiate around September 2013, probably not by coincidence and begging the question of human issues more than technical ones.