text:
American Wonders, Revisited
Our nation's most iconic vacation destinations are that much more awe-inspiring when you experience them up close under your own steam.
By Sarah Tuff Dunn | December 2015
America's greatest natural wonders are the subjects of endless vacation-photo backdrops. But you can't really experience the full glory of these places from a scenic overlook.
To get the best of them, you have to get out into them. And to do that takes muscle and an appetite for exploration.
From the California redwoods to Kentucky caves, active adventures abound. Most offer you the opportunity to move your body as a means to not only reach your destination, but also to amplify your enjoyment of these popular vacation spots.
Activities like hiking, kayaking, climbing, skiing, and rappelling (to name just a few) create a multisensory, kinesthetic connection to your surroundings, helping to stamp an indelible impression you'll carry with you long after you return home.
No matter which region of the country you find yourself in, there's no shortage of unique landscapes awaiting exploration.
"Ours is a large country graced with a stunning diversity," says Bill Flower, the former Outings Committee chair for the Sierra Club. Here are seven destinations Flower deems "some of the most remarkable places here or anywhere else on Earth."
Where: Niagara Falls, N.Y.
Who: Daredevils and Niagara go hand-in-hand, but this adventure is for anyone who can put one foot in front of the other — and who doesn't mind the cold.
Why: You're likely familiar with the splendor of the falls in summer, but Niagara (the collective name for the three falls straddling the United States–Canada border) is no less magnificent in the off-season. Each winter, wind, water, and wicked low temperatures combine to create crystalline natural snow and ice sculptures. Take in the sights, then warm up by cross-country skiing or snowshoeing in nearby parks. With the whisper-quiet hush instead of the din of tourist crowds — the Maid of the Mist boat tour and other nearby attractions are in hibernation — the cascades are even more magical in the coldest of temperatures.
When: Niagara is at its loveliest and most peaceful in winter, when the tourists leave and Mother Nature takes over, leaving a breathtakingly beautiful sight, explains Angela Berti of Niagara Falls State Park. Select trails are open throughout the cold season.
How: Rent snowshoes or cross-country skis from Reinstein Woods Nature Preserve and Environmental Educational Center (dec.ny.gov), about a 40-minute drive from the 400-acre Niagara Falls State Park (niagarafallsstatepark.com).
Cost: $5 per pair for snowshoe or cross-country ski rentals.
Difficulty: Moderate, depending on snow and ice conditions.
Where: Olympic Peninsula, Wash.
Who: Whitewater fans and other river rats.
Why: Twelve to 14 feet — yes, feet — of rain fall here each year. Embrace the wetness by rafting class II and III rapids along the glacier-fed, 50-mile-long Hoh River, a turquoise ribbon that spills from the 7,000-foot Mount Olympus and weaves among the deciduous and coniferous trees.
When: February through April for more challenging rapids (ages 10-plus); May through October for more placid ripples (ages 5-plus).
How: Reserve a half-day or daylong trip with Rainforest Paddlers (rainforestpaddlers.com).
Cost: $44 for a half day; $79 for a full day, including lunch.
Difficulty: Moderate; the rapids are appropriate for novice and intermediate rafters.
Where: Mount Desert Island, Maine
Who: Nature lovers, early risers, and anyone else who'd prefer to escape from the crowds that can clog other national parks.
Why: Cadillac Mountain, the 1,530-foot peak in Acadia National Park, is the highest point on the Eastern Seaboard, but it's only one of Acadia's highlights. Tidal pools, paddling-perfect ponds, and historic carriage roads built by John D. Rockefeller are set among 47,000 acres of raw coastline and wild woodland. Hike the 5.4-mile Schooner Head Trail and the 4.4-mile Cadillac Mountain North Ridge Trail, which overlooks Frenchman Bay; cycle around Seal Harbor; or undertake a crossing of Long Pond.
When: Any time. But be prepared for temps as low as 14 degrees F in colder months.
How: The park headquarters office offers maps and information (nps.gov/acad).
Cost: Seven-day park passes are $25 per vehicle ($12 per person on bike or foot); bikes are $23 per day, and watersports rentals start at $30 (nationalparkcanoerental.com).
Difficulty: As easy as you please. Those who want more challenge can hike and camp in Acadia's more remote backcountry.
This article originally appeared as part of "American Wonders Revisited" in the December 2015 issue of Experience Life. To order a back issue, call 800-897-4056 (press option 3 when prompted). To get all the articles from each issue of Experience Life, subscribe online at ELmag.com/subscribe.
Sarah Tuff Dunn Sarah Tuff Dunn writes on fitness, health, and travel from Burlington, Vt.
A Grand Adventure
By Sarah Tuff Dunn
Test your physical strength on a trek below the rim of one of America's most challenging natural wonders: the Grand Canyon.
Habit-Changing Vacations
By Laurel Kallenbach
New-experience getaways that help you leave old behaviors behind.
The Unexpected Gifts of Travel
By Anneli Rufus
Why a change of scenery can make us feel better about everything — including ourselves.


text:
Zaian War
Part of the North African theatre of World War I (to 1918)
Map showing the area in which the war was fought
1914 (1914)–1921 (1921)
French protectorate of Morocco
Zaian Confederation
Varying other Berber tribes
Supported during the First World War by the Central Powers
Paul Prosper Henrys
Joseph-François Poeymirau
Mouha ou Hammou Zayani
Moha ou Said
Ali Amhaouch
95,000 French troops in all of Morocco in 1921[1] Up to 4,200 tents (approximately 21,000 people) of Zaians at the start of the war[2]
French dead in the Middle Atlas to 1933:[3]
82 French officers
700 European regulars
1,400 African regulars
2,200 goumiers and partisans
North African operations during World War I
Senussi Campaign
Action of Agagia
Volta-Bani War
Darfur Campaign
Kaocen Revolt
Franco-Moroccan conflicts
Larache expedition (1765)
Conquest of Algeria (1830–47)
Franco-Moroccan War (1844)
Bombardment of Salé (1851)
Conquest of Morocco (1911–12)
Zaian War (1914–21)
Rif War (1920–26)
Ifni War (1957–58)
The Zaian (or Zayan) War was fought between France and the Zaian confederation of Berber tribes in Morocco between 1914 and 1921. Morocco had become a French protectorate in 1912, and Resident-General Louis-Hubert Lyautey sought to extend French influence eastwards through the Middle Atlas mountains towards French Algeria. This was opposed by the Zaians, led by Mouha ou Hammou Zayani. The war began well for the French, who quickly took the key towns of Taza and Khénifra. Despite the loss of their base at Khénifra, the Zaians inflicted heavy losses on the French, who responded by establishing groupes mobiles, combined arms formations that mixed regular and irregular infantry, cavalry and artillery into a single force.
The outbreak of the First World War proved significant, with the withdrawal of troops for service in France compounded by the loss of more than 600 French killed at the Battle of El Herri. Lyautey reorganised his available forces into a "living barricade", consisting of outposts manned by his best troops protecting the perimeter of French territory with lower quality troops manning the rear-guard positions. Over the next four years the French retained most of their territory despite intelligence and financial support provided by the Central Powers to the Zaian Confederation and continual raids and skirmishes reducing scarce French manpower.
After the signing of the Armistice with Germany in November 1918, significant forces of tribesmen remained opposed to French rule. The French resumed their offensive in the Khénifra area in 1920, establishing a series of blockhouses to limit the Zaians' freedom of movement. They opened negotiations with Hammou's sons, persuading three of them, along with many of their followers, to submit to French rule. A split in the Zaian Confederation between those who supported submission and those still opposed led to infighting and the death of Hammou in Spring 1921. The French responded with a strong, three-pronged attack into the Middle Atlas that pacified the area. Some tribesmen, led by Moha ou Said, fled to the High Atlas and continued a guerrilla war against the French well into the 1930s.
1 Origins
2 Khénifra campaign
2.1 Groupes mobiles
3 First World War
3.1 Battle of El Herri
3.2 After El Herri
3.3 The Central Powers in Morocco
4 Post-war conflicts
Main article: French conquest of Morocco
General Mangin entering Marrakesh on 9 September 1912
The signing of the Treaty of Fez in 1912 established a French protectorate over Morocco.[4] The treaty had been prompted by the Agadir Crisis of 1911, during which French and Spanish troops had been sent to Morocco to put down a rebellion against Sultan Abdelhafid. The new French protectorate was led by a resident-general, Louis-Hubert Lyautey, and adopted the traditional Moroccan way of governing through the tribal system.[4] Upon taking up his post Lyautey replaced Abdelhafid with his brother, Yusef.[5] The tribes took offence at this, installing their own Sultan, Ahmed al-Hiba, in Marrakesh and taking eight Europeans captive.[5] Lyautey acted quickly against the revolt, dispatching General Charles Mangin and 5,000 troops to retake the town. Mangin's men were highly successful, rescuing the captives and inflicting heavy casualties on vastly superior numbers of tribesmen for the loss of 2 men killed and 23 wounded.[5] Al-Hiba escaped to the Atlas mountains with a small number of his followers and opposed French rule until his death in 1919.[6]
General Lyautey photographed in 1908–09
A popular idea among the public in France was to possess an unbroken stretch of territory from Tunis to the Atlantic Ocean, including expansion into the "Taza corridor" in the Moroccan interior.[7] Lyautey was in favour of this and advocated French occupation of the Middle Atlas mountains near Taza, through peaceful means where possible.[8] This French expansion into the Middle Atlas was strongly opposed by the "powerful Berber trinity" of Mouha ou Hammou Zayani, leader of the Zaian Confederation; Moha ou Said, leader of the Aït Ouirra; and Ali Amhaouch, a religious leader of the Darqawa variant of Islam prevalent in the region.[9][10]
Hammou commanded between 4,000 and 4,200 tents[nb 1] of people and had led the Zaians since 1877, opposing the French since the start of their involvement in Morocco.[2] An enemy of the French following their deposing of Sultan Abdelhafid, who was married to Hammou's daughter, he had declared a holy war against them and intensified his tribe's attacks on pro-French (or "submitted") tribes and military convoys.[2][12] Said was an old man, who was held in good standing by tribesmen across the region and had formerly been a caïd (a local governor with almost absolute power) for the Moroccan government, even serving in the army of Sultan Abdelaziz against a pretender at Taza in 1902.[13][14][15] Despite initially being open to negotiations with the French, pressure from pro-war chiefs and the fear of ridicule from his tribesmen had dissuaded him.[13][16][17] Amhaouch was a strong and influential man, described by French officer and explorer René de Segonzac as one of the "great spiritual leaders of Morocco" and the "most powerful religious personality of the south east".[9] The French had attempted to persuade the Zaians to submit since 1913 with little success; most tribes in the confederation remained opposed to French rule.[18]
Lyautey's plans for taking Taza also extended to capturing Khénifra, Hammou's headquarters. He had been advised by his political officer, Maurice Le Glay that doing so would "finish him off definitively" and cut the Zaians off from support of other tribes.[9] The French outpost at nearby Kasbah Tadla had recently been attacked by Said and subsequent peace negotiations led by Lyautey's head of intelligence, Colonel Henri Simon, had achieved little.[19] As a result, Mangin was authorised to lead a retaliatory raid to Said's camp at El Ksiba but, despite inflicting heavy casualties, was forced to withdraw with the loss of 60 killed, 150 wounded and much equipment abandoned.[19] Having failed to make any impression on the Zaians through negotiation in May 1914, Lyautey authorised General Paul Prosper Henrys to take command of all French troops in the area and launch an attack on Taza and Khénifra.[2][8] Henrys captured Taza within a few days using units drawn from garrisons in Fez, Meknes, Rabat and Marrakesh and then turned his attention to Khénifra.[18][20]
Khénifra campaign
The routes of the French columns that marched on Khénifra
Henrys planned his assault on Khénifra to begin on 10 June 1914 with the dispatch of three columns of troops, totalling 14,000 men equipped with wireless radios and supported by reconnaissance aircraft.[8] One column was to set out from Meknes under the command of Lieutenant-Colonel Henri Claudel, another from Rabat under Lieutenant-Colonel Gaston Cros and the third from Kasbah Tadla under Colonel Noël Garnier-Duplessix.[21] Henrys took overall command, directing the forces from an armoured car within the Claudel column.[21] Aware that he knew little of the terrain or the allegiance of local tribes Henrys offered a generous set of terms for tribesmen who submitted to French rule: they would have to surrender only their rapid firing rifles and any captured French supplies, and pay a small tax in return for protection.[21] He also set aside substantial funds to bribe informants and tribal leaders.[21]
Despite these measures, Claudel's column came under attack before it even left Meknes, although it was the largest and intended as a diversion.[22] Hammou's forces attacked their camp on three separate nights, inflicting losses of at least one officer and four men killed and nineteen injured, but leaving the other two columns unopposed.[22] Claudel launched a counterattack on 10 June while Hammou was preparing a fourth attack, sweeping the Zaians away with artillery and ensuring little resistance for his march to Khénifra on the next day.[22] After enduring some sniping attacks in Teguet, Claudel's cavalry crossed the Oum er Rbia at el Bordj and advanced to the outskirts of Khénifra.[22] The rest of the column joined them on 12 June, fighting off Zaian attacks on the way and meeting up with the other two columns, finding the town emptied of people and raising the French flag.[22] The column had lost two men killed in the march.[22]
A modern image showing the landscape near Khénifra
The columns experienced repeated, strong attacks by Zaian tribesmen that day, repelled by late afternoon at the cost of five men killed and nineteen wounded.[22] Further attacks on the nights of 14 and 15 June were repulsed by artillery and machine gun fire, directed by searchlights.[23] Henrys then dispatched two columns south to the Zaian stronghold of Adersan to burn houses, proving his military abilities but not provoking a decisive confrontation with the tribes, who returned to guerrilla warfare tactics.[23] In response all French-controlled markets were closed to the Zaians and their trade convoys were intercepted.[23]
Henrys became aware of a Zaian presence at el Bordj and sent a column to attack them on 31 June. South of el Bordj the French came under heavy fire from tribesmen with modern rifles and resorted to bayonet charges to clear the way.[23] The encounter was Henrys' first major engagement with the Zaians and his losses were high, 1 officer and 16 men killed and a further 2 officers and 75 men wounded.[24] Zaian losses were much higher: the French counted at least 140 dead remaining on the battlefield, and considered the battle a victory.[24] Henrys expected a pause in activity while the Zaians recovered, but instead Hammou stepped up attacks on the French.[24] Just four days later an attack on a French convoy by 500 mounted tribesmen was only repulsed after several hours by more bayonet charges.[24] French losses were again significant with one officer and ten men killed and thirty men wounded.[24]
Groupes mobiles
File:Senegalese troops en route to Morocco 1908.png
A near-contemporary depiction of Senegalese troops en route to Morocco
In light of the increased attacks in the Khénifra area Henrys established three groupes mobiles, made up of troops mostly drawn from the Army of Africa.[25] Each groupe was designed to be highly mobile and typically consisted of several battalions of regular infantry (Algerian and Senegalese Tirailleurs or French Foreign Legion troops), a squadron of cavalry (Algerian Spahis), a few batteries of artillery (field or mountain), a section of Hotchkiss machine guns and a mule train for supplies under the overall leadership of a French senior officer.[5][26] In addition each groupe mobile would have one or two goums (informal groups of around 200 men) of goumiers, irregular tribal auxiliaries, under the leadership of a French intelligence officer.[27] The goums were used for intelligence gathering operations and in areas of difficult terrain.[27]
A four-battalion-strong groupe mobile was established at Khénifra, under Lieutenant-Colonel René Laverdure; one based to the west under Claudel and one to the east under Garnier-Duplessix.[24] In addition fortified posts were established at M'Rirt and Sidi Lamine with the areas between patrolled by goumiers to protect convoys and submitted tribes from attack.[25] Increasing attacks on Khénifra throughout July, repelled only by concentrated artillery and machine gun fire, left Henrys concerned that a combined force of tribesmen could threaten the town and the submitted tribes.[28] This fear was partially allayed by the separate defeats of Hammou and Amhaouch by the groupes mobiles of Claudel and Garnier-Duplessix and by increasing numbers of auxiliaries becoming available from newly submitted tribes through the levy system.[25]
Claudel and Garnier-Duplessix were ordered to patrol the French bank of the Oum er Rbia and attempt to separate the Zaians from the Chleuh to the south while Henrys planned for an advance through the Middle Atlas to the Guigou River.[29] These operations were halted by the reduction in forces imposed on him by the outbreak of the First World War in Europe.[29]
Lyautey received orders from Army headquarters in Paris on 28 July 1914 the day the First World War began, requesting the dispatch of all available troops to France in anticipation of a German invasion and the withdrawal of his remaining forces to more defensible coastal enclaves.[30] The French government justified this stance by stating that the "fate of Morocco will be determined in Lorraine".[31] Lyautey, who had lost most of his own possessions when his house in Crévic had been burnt to the ground by advancing German forces, was keen to support the defence of France and within a month had sent 37 infantry and cavalry battalions and six artillery batteries to the Western Front – more than had been requested of him.[30][32] A further 35,000 Moroccan labourers were recruited by Lyautey over the course of the war for service in France.[33]
File:1914 senegalese tiralleurs.jpg
A 1914 drawing of Senegalese Tirailleurs
Nevertheless, Lyautey did not wish to abandon the inland territory his men had fought so hard for, stating that if he withdrew "such a shock would result immediately all over Morocco ... that a general revolt would arise under our feet, on all our points".[30] Left with just 20 battalions of legionnaires (mainly German and Austrian[nb 2]), military criminals of the Infanterie Légère d'Afrique, territorial reservists, Senegalese Tirailleurs and goumiers, he switched from the offensive to a long-term strategy of "active defence".[31][35] Lyautey withdrew all non-essential personnel from his rear garrisons, brought in elderly reservists from France and issued weapons and elements of military dress to civilians in an attempt to convince the tribes that the French army in Morocco was as strong as before.[31][36] Lyautey referred to this move as similar to hollowing out a lobster while leaving the shell intact.[29] His plan depended on holding a "living barricade" of French outposts running from Taza in the north through Khenifra, Kasbah Tadla and Marrakesh to Agadir on the Atlantic coast.[29]
Lyautey and Henrys intended to hold the Berbers in their current positions until they had sufficient resources to return to the offensive.[24] The recent French advances and troop withdrawals had left Khénifra badly exposed and from 4 August – the day two battalions of infantry left the garrison for France – the Zaian tribes launched a month-long attack on the town, supply convoys and withdrawing French troops "without interruption".[18][29] Lyautey was determined to hold Khénifra to use as a bridgehead for further expansion of French territory and referred to it as a bastion against the "hostile Berber masses" upon which the "maintenance of [his] occupation" depended.[18] Attacks on Khénifra threatened the vital communication corridor between French forces in Morocco and those in Algeria.[18] To relieve pressure on the town, Claudel and Garnier-Duplessix's groupes mobiles engaged Hammou and Amhaouch's forces at Mahajibat, Bou Moussa and Bou Arar on 19, 20 and 21 August, inflicting "considerable losses".[29] This, combined with the reinforcement of Khenifra on 1 September, led to reduced attacks, decreasing to a state of "armed peace" by November.[29]
File:German POWs in morocco WWI.jpg
German prisoners of war at work in Morocco
Henrys began to move towards a more offensive posture, ordering mobile columns to circulate through the Middle Atlas and mounted companies to patrol the plains.[35] This was part of his plan to maintain pressure on Hammou, who he considered to be the linchpin of the "artificial" Zaian Confederation and responsible for their continued resistance.[24][37] Henrys was counting on the onset of winter to force the Zaians from the mountains to their lowland pastures where they could be confronted or persuaded to surrender.[37] In some cases the war assisted Lyautey, allowing him a freer hand in his overall strategy, greater access to finance and the use of at least 8,000 German prisoners of war to construct essential infrastructure.[38][39] In addition the increased national pride led many middle-aged French immigrants in Morocco to enlist in the army and, though they were of poor fighting quality, Lyautey was able to use these men to maintain the appearance of a large force under his command.[40]
Battle of El Herri
Main article: Battle of El Herri
A modern image of the Oum er Rbia at Khénifra
When Henrys had successfully repulsed the attacks on Khénifra, he believed he had the upper hand, having proven that the reduced French forces could resist the tribesmen.[41] The Zaians were now contained within a triangle formed by the Oum er Rbia River, the Serrou River and the Atlas Mountains, and were already in dispute with neighbouring tribes over the best wintering land.[41] Hammou decided to winter at the small village of El Herri, 15 kilometres (9 miles) from Khénifra, and established a camp of around 100 tents there.[41][42] Hammou had been promised peace talks by the French, and Lyautey twice refused Laverdure permission to attack him and ordered him to remain on the French bank of the Oum er Rbia.[41][42][43] On 13 November Laverdure decided to disobey these orders and marched to El Herri with almost his entire force, some 43 officers and 1,187 men with supporting artillery and machine guns.[44] This amounted to less than half the force he had in September, when he had last been refused permission to attack.[45]
Laverdure's force surprised the Zaian camp, mostly empty of fighting men, at dawn.[46] A French cavalry charge, followed up with infantry, successfully cleared the camp.[47] After capturing two of Hammou's wives and looting the tents the French started back for Khénifra.[43] The Zaians and other local tribes, eventually numbering 5,000 men, began to converge on the French column and began harassing its flanks and rear.[43][47][48] The French artillery proved ineffective against dispersed skirmishers and at the Chbouka river the rearguard and gun batteries found themselves cut off and overrun.[47] Laverdure detached a small column of troops to take his wounded to Khénifra, remaining behind with the rest of the force.[47] Laverdure's remaining troops were surrounded by the Zaians and were wiped out by a mass attack of "several thousand" tribesmen.[46][47]
The wounded and their escort reached Khenifra safely by noon, narrowly outpacing their pursuers, who had stopped to loot the French dead.[42][47] This force of 431 able-bodied men and 176 wounded were the only French survivors of the battle.[47] The French lost 623 men on the battlefield, while 182 Zaian were killed.[42][49] The French troops also lost 4 machine guns, 630 small arms, 62 horses, 56 mules, all of their artillery and camping equipment and much of their personal belongings.[44][50]
After El Herri
File:Fflmorocco.png
A drawing showing French Foreign Legion troops in action against tribesmen in Morocco
The loss of the column at El Herri, the bloodiest defeat of a French force in Morocco, left Khénifra almost undefended.[51] The senior garrison officer, Captain Pierre Kroll, had just three companies of men to protect the town.[43][47] He managed to inform Lyautey and Henrys of the situation by telegraph before the town came under siege from the Zaians.[43][46] Henrys determined to act quickly against the Zaians to prevent Laverdure's defeat from jeopardising the French presence in Morocco, dispatching Garnier-Duplessix's groupe mobile to Khénifra and forming another groupe in support at Ito under Lieutenant-Colonel Joseph Dérigoin.[43][47] Garnier-Duplessix fought his way to the town, relieved it on 16 November, and was joined by Henrys shortly afterwards.[44] The 6th battalion of the 2nd French Foreign Legion Regiment also reached the town, having fought off Zaian attacks during their march from M'Rirt.[35] Henrys led excursions from Khénifra to El Herri as a show of force and to bury their dead, some of whom had been taken as trophies by Hammou to encourage support from other tribes.[44][50]
The Zaian victory at El Herri, combined with slow French progress on the Western Front and the siding of the Muslim Ottoman Empire with the Central Powers, led to an increase in recruits for the tribes and greater co-operation between Hammou, Amhaouch and Said.[52] To counter this Henrys undertook a reorganisation of his forces, forming three military districts centred on Fez, Meknes and Tadla-Zaian (the Khénifra region), the latter under the command of Garnier-Duplessix.[52] Henrys aimed to maintain pressure on Hammou through an economic blockade and the closure of markets to unsubmitted tribes.[52] He imposed a war penalty, in the form of money, horses and rifles, on submitting tribes, believing that their submission would last only if they paid for it.[53] Few tribes took up Henrys' offer and the Zaians continued to cross the Rbia and attack French patrols.[53]
The French returned to the offensive in March with Dérigoin's group sweeping along the French bank of the Rbia, north of Khénifra, and Garnier-Duplessix the left.[53] Dérigoin faced and drove off only a small Zaian force, but Garnier-Duplessix faced a more significant force – his troops were almost overrun by a large mounted group but managed to repulse them, inflicting "serious losses" in return for French casualties of one man killed and eight wounded.[53] Garnier-Duplessix crossed the Rbia again in May to confiscate crops, and was attacked there by a force of 4–5,000 tribesmen at Sidi Sliman, near Kasbah Tadla.[54][55] He repulsed them with artillery and counterattacked successfully over the course of a two-day engagement, killing 300 of the attackers and wounding 400 at the cost of 3 French dead and 5 wounded.[54][55] This victory restored the image of French superiority and led to an increase in tribal submissions, the withdrawal of Said's forces further into the mountains and a six-month period of relative peace.[54] In recognition of this Garnier-Duplessix was promoted to major-general.[54]
The peace was broken on 11 November 1915 by an attack on a supply convoy headed for Khénifra by 1,200–1,500 Zaians and allied tribesmen.[54] The Moroccans pressed to within 50 metres (55 yards) of the French, and Garnier-Duplessix, in command of the convoy, was forced to resort to the bayonet to push them back.[54] French casualties amounted to just 3 killed and 22 wounded but Henrys was concerned by the influence that Hammou continued to hold over other Berber tribes.[54] In retaliation Henrys took both groupes mobiles across the Rbia and bombarded the Zaian camp, inflicting casualties but making little impression on their will to fight.[56] The Zaians recrossed the Rbia in January 1916, camping in French territory and raiding the submitted tribes.[56] Feeling that his communications with Taza were threatened Henrys withdrew his groupes to the Khénifra area, both of them coming under attack en route.[56] At M'Rirt a sizeable Zaian attack was repulsed with 200 casualties but the French suffered the loss of one officer and 24 men killed and 56 wounded.[56]
File:Goumiers morocco.png
A 1907 drawing of mounted goumiers attacking Moroccan tribesmen
Lyautey had successfully retained the territory he had captured before the war but was of the opinion that he could not advance any further without risking "an extremely painful" mountain conflict.[56] He faced having his troops withdrawn for service on the Western Front and being left with what he described as "degenerates and outcasts", a loss only partially mitigated by the expansion of the irregular tribal units to 21 goums in strength.[57][58] Henrys accepted an offer of a position in France and was replaced by Colonel Joseph-François Poeymirau, a keen follower of Lyautey who had served as Henrys' second in command at Meknes.[59] Lyautey was offered the post of Minister of War at the invitation of Prime Minister Aristide Briand, which he accepted on 12 December 1916.[56][60] Lyautey was replaced, at his request, by General Henri Gouraud, who had experience fighting alongside Lyautey in Morocco and who had recently returned from the Dardanelles, where he had lost his right arm.[60][61] Lyautey soon became disillusioned with French tactics in Europe, the disunity prevailing between the Allies and his position as a symbolic figurehead of the government.[60][61][62] He was unfamiliar with dealing with political opposition and resigned on 14 March 1917, after being shouted down in the Chamber of Deputies.[63] The government could not survive the resignation of such a senior cabinet member and Briand himself resigned on 17 March, to be replaced by Alexandre Ribot.[63]
Lyautey returned to his former position in Morocco at the end of May and immediately decided on a new strategy. He concentrated his forces in the Moulouya Valley, convinced that the submission of the tribes in this area would lead to the collapse of the Zaian resistance.[60][62][64] In preparation for this new offensive Poeymirau established a French post at El Bekrit, within Zaian territory, and forced the submission of three local tribes.[59] He then used this post to protect his flanks during an advance south-eastwards into the valley, intending to meet with a column led by Colonel Paul Doury, advancing north-west from Boudenib.[59][65] The two columns met at Assaka Nidji on 6 June, a moment which represented the establishment of the first French-controlled route across the Atlas mountains, and earned Poeymirau promotion to brigadier-general.[66] A defensive camp was soon established at Kasbah el Makhzen, and Doury began construction on a road that he promised would be traversable by motor transport by 1918.[59]
By late 1917 motorised lorries were able to traverse much of the road, allowing the French to quickly move troops to areas of trouble and supply their garrisons in eastern Morocco from the west rather than over long routes from the Algerian depots.[66] A secondary road was constructed, leading southwards from the first along the Ziz River, that allowed Doury to reach Er-Rich in the High Atlas, and major posts were established at Midelt and Missour.[66] The Zaians refused to be drawn into attacking the fortified posts that the French built along their new roads, though other tribes launched attacks that summer after rumours of French defeats on the European front.[64] In one instance, in mid-June, it took Poeymirau's entire groupe three days to restore control of the road after an attack.[64]
Doury had expanded the theatre of operations, against Lyautey's orders, by establishing a French mission at Tighmart, in the Tafilalt region, in December 1917 in reaction to a rumoured German presence there.[64] The land here, mainly desert, was almost worthless to the French and Lyautey was keen for his subordinates to focus on the more valuable Moulouya Valley.[67] Local tribes resisted the French presence, killing a translator working at the mission in July 1918.[67] Doury sought to avenge this act on 9 August by engaging up to 1,500 tribesmen, led by Sidi Mhand n'Ifrutant, at Gaouz with a smaller French force that included artillery and aircraft support.[67][68] Entering a thick, jungle-like date palm oasis, one subgroup of Doury's force suffered a close, hard-fought action, hampered by exhaustion and poor supply lines.[64][69] The whole force suffered casualties of 238 men killed and 68 wounded, the worst French losses since the disaster at El Herri, and also lost much of their equipment and transport.[64][70] Lyautey was doubtful of Doury's claim to have almost wiped out his foe, and in response chastised him for his rash action in "this most peripheral of zones" and placed him under Poeymirau's direct command.[67][70] Thus, as the war in Europe was drawing to a close in the early summer of 1918, the French remained hard pressed in Morocco. Despite the death of Ali Amhaouch by natural causes, significant numbers of tribesmen under the leadership of Hammou and Said continued to oppose them.[64]
The Central Powers in Morocco
File:Abdelhafid 1914.jpg
Former Sultan Abdelhafid in 1914
The Central Powers attempted to incite unrest in the Allied territories in Africa and the Middle East during the war, with the aim of diverting military resources away from the Western Front.[71] German intelligence had identified Northwest Africa as the "Achilles' heel" of the French colonies, and encouraging resistance there became an important objective.[72] Their involvement began in 1914, with the Germans attempting to find a suitable Moroccan leader that they could use to unite the tribes against the French.[73] Their initial choice, former Sultan Abdelaziz, refused to co-operate and moved to the south of France to prevent any further approaches.[73] Instead they entered negotiations with his successor Abdelhafid. He initially co-operated with the Germans, renouncing his former pro-Allied stance in autumn 1914 and moving to Barcelona to meet with officials from Germany, the Ottoman Empire and the Moroccan resistance.[74] During this time he was also selling information to the French.[74] These mixed loyalties came to light when he refused to board a German submarine headed for Morocco, and the Central Powers decided he was of no further use.[74] Abdelhafid then attempted to extort money from the French intelligence services, who responded by halting his pension and arranging his internment at El Escorial.[74] He was later awarded a stipend by Germany in return for his silence on the matter.[74]
The failure to find a suitable leader caused the Germans to alter their plans from a widespread insurrection in Morocco to smaller-scale support of the existing resistance movement.[74] German support included the supply of military advisers and Foreign Legion deserters to the tribes as well as cash, arms and ammunition.[75] Money (in both pesetas and francs) was smuggled into Morocco from the German embassy at Madrid.[76] The money was transferred to Tétouan or Melilla by boat or wired through the telegraph before being smuggled to the tribes, who each received up to 600,000 pesetas per month.[76] Weapons arrived through long-established routes from Spanish Larache or else purchased directly from French gun runners or corrupt Spanish Army troops.[77] The Germans found it hard to get resources to the Zaians in the Middle Atlas due to the distances involved and most of what did get through went to Said's forces.[78] German attempts to distribute supplies inland were frustrated when many tribes hoarded the best resources.[79] Ammunition remained scarce in the Middle Atlas, and many were forced to rely on locally manufactured gunpowder and cartridges.[79]
The Ottoman Empire also supported the Moroccan tribesmen in this period, having provided military training to them since 1909.[80] They co-operated with German intelligence to write and distribute propaganda in Arabic, French and the Middle Atlas Berber dialect.[81] Much of the Ottoman intelligence effort was coordinated by Arab agents operating from the embassy in Madrid and at least two members of the Ottoman diplomatic staff there are known to have seen active service with the tribes in Morocco during the war.[82] Ottoman efforts in Morocco were hindered by internal divisions among the staff, disagreements with their German allies and the outbreak of the Arab Revolt in 1916, with which some of the embassy staff sympathised.[82] These problems led many of the Ottoman diplomatic corps in Spain to leave for America in September 1916, bringing to an end many of the significant Ottoman operations in Morocco.[83]
File:Casablanca fair 1915 poster.png
Poster advertising the 1915 Casablanca Fair
French intelligence forces worked hard to combat the Central Powers and to win the support of the Moroccan people. A series of commercial expositions, such as the Casablanca Fair of 1915, were held to demonstrate the wealth of France and the benefits of co-operation.[84] In addition to stepping up their propaganda campaign and increasing the use of bribes to convince tribes to submit, the French established markets at their military outposts and paid Moroccans to undertake public works.[84] Islamic scholars were also encouraged to issue fatwās supporting the Moroccan Sultan's declaration of independence from the Ottoman Empire.[85]
French and British intelligence agents co-operated in French and Spanish Morocco and Gibraltar, tracking Ottoman and German agents, infiltrating the advisers sent to the tribes and working to halt the flow of arms.[77][86] German citizens in Morocco were placed under careful scrutiny and four were executed within days of the war's start.[87] The French broke the codes used by the German embassy and were able to read almost every communication sent from there to the General Staff in Berlin.[86] Bribes paid to staff at the Ottoman mission to Spain secured intelligence on the Central Powers' plans for Morocco.[86]
Although the efforts of the Central Powers caused a resurgence in resistance against French rule, they were largely ineffective, falling short of the planners' aims of a widespread jihad.[4][88][89] There were few cases of mass civil disorder, France was not required to reinforce the troops stationed in Morocco, and the export of raw materials and labour for the war effort continued.[88] Although they were never able to completely stem the flow of arms, despite considerable effort, the French were able to limit the supply of machine guns and artillery.[79][90] The tribes were thus unable to face the French in direct confrontation and had to continue to rely on ambushes and raids.[90] This contrasted with the Spanish experience in the Rif War of 1920–26, in which tribes with access to such weapons were able to inflict defeats upon the Spanish Army in the field, such as at the Battle of Annual.[90]
Post-war conflicts
A contemporary depiction of Thami El Glaoui, Pasha of Marrakesh
The heavy French losses at the Battle of Gaouz encouraged an increase in tribal activity across the south-east of Morocco, threatening the French presence at Boudenib.[1][70] Poeymirau was forced to withdraw garrisons from outlying posts in the Tafilalt, including that at Tighmart, to concentrate his force and reduce the risk of further disasters.[70] Lyautey authorised only a series of limited offensives, such as the razing of villages and gardens, the primary aim of which was to emphasise French military superiority.[91] The French struggled to move troops through the mountain passes from the Moulouya Valley due to heavy snows and attacks on their columns, and Lyautey, to his embarrassment, was forced to request reinforcements from Algeria.[70] By October the situation had stabilised to the extent that Poeymirau was able to withdraw his troops to Meknes, but a large-scale uprising in January 1919 forced his return.[91] Poeymirau defeated n'Ifrutant in battle at Meski on 15 January, but was seriously wounded in the chest by the accidental explosion of an artillery shell and was forced to hand command to Colonel Antoine Huré.[70] Lyautey then received assistance from Thami El Glaoui, a tribal leader who Lyautey had made Pasha of Marrakesh after the uprising of 1912.[92] El Glaoui owed his increasing wealth (when he died in 1956 he was one of the richest men in the world) to corruption and fraud, which the French tolerated in return for his support.[93][94] Thus committed to Lyautey's cause, El Glaoui led an army of 10,000 men, the largest Moroccan tribal force ever seen, across the Atlas to defeat anti-French tribesmen in the Dadès Gorges and to reinforce the garrison at Boudenib on 29 January.[1][70] The uprising was over by 31 January 1919.[91]
A French Foreign Legion unit on the march in Morocco, 1920
The conflict in the Tafilalt distracted the French from their main war aims, draining French reinforcements in return for little economic gain and drawing comparisons to the recent Battle of Verdun.[91] Indeed, the Zaians were encouraged by French losses in the area to renew their attacks on guardposts along the trans-Atlas road.[91] The French continued to hope for a negotiated end to the conflict and had been in discussions with Hammou's close relatives since 1917.[91] Indeed, his nephew, Ou El Aidi, had offered his submission in exchange for weapons and money but had been refused by the French who suspected he wanted to fight with his cousin, Hammou's son, Hassan.[91] With no progress in these negotiations Poeymirau moved against the tribes to the north and south of Khénifra in 1920, the front in this area having remained static for six years.[95] Troops were brought in from Tadla and Meknes to establish blockhouses and mobile reserves along the Rbia to prevent the Zaians crossing to use the pastures.[95] The French were opposed vigorously but eventually established three blockhouses and forced some of the local tribes to submit.[95] French successes in the Khénifra region persuaded Hassan and his two brothers to submit to the French on 2 June 1920, having returned some of the equipment captured at El Herri.[96][97] Hassan was soon appointed Pasha of Khénifra and his 3,000 tents were brought under French protection in an expanded zone of occupation around the Rbia.[96]
Hammou's son, Hassan, surrendering to General Poeymirau
Following the submission of his sons, Hammou retained command of only 2,500 tents and in Spring 1921 was killed in a skirmish with other Zaian tribes that opposed continued resistance.[96] The French seized the opportunity to launch an assault on the last bastion of Zaian resistance, located near El Bekrit.[96] In September a three-pronged attack was made: General Jean Théveney moved west from the El Bekrit settlement, Colonel Henry Freydenberg moved east from Taka Ichian and a third group of submitted tribesmen under Hassan and his brothers also took part.[96][98] Théveney encountered resistance from the Zaians in his area but Freydenberg was almost unopposed and within days all resistance was put down.[98] After seven years of fighting the Zaian War was ended, though Lyautey continued his expansion in the area, promising to have all of "useful Morocco" under French control by 1923.[68][98][99] Lyautey had been granted the dignity of a Marshal of France in 1921 in recognition of his work in Morocco.[100]
Map depicting the staged pacification of Morocco through to 1934
In Spring 1922, Poeymirau and Freydenberg launched attacks into the headwaters of the Moulouya in the western Middle Atlas and managed to defeat Said, the last surviving member of the Berber triumvirate, at El Ksiba in April 1922.[98][101] Said was forced to flee, with much of the Aït Ichkern tribe, to the highest mountains of the Middle Atlas and then into the High Atlas.[102] Lyautey then secured the submission of several more tribes, constructed new military posts and improved his supply roads; by June 1922, he had brought the entire Moulouya Valley under control and pacified much of the Middle Atlas.[98] Limited in numbers by rapid post-war demobilisation and commitments to garrisons in Germany, he determined not to march through the difficult terrain of the High Atlas but to wait for the tribes to tire of the guerrilla war and submit.[102][103] Said never did so, dying in action against a groupe mobile in March 1924, though his followers continued to cause problems for the French into the next decade.[102][104] Pacification of the remaining tribal areas in French Morocco was completed in 1934, though small armed gangs of bandits continued to attack French troops in the mountains until 1936.[105][106] Moroccan opposition to French rule continued, a plan for reform and return to indirect rule was published by the nationalist Comité d'Action Marocaine (CAM) in 1934, with significant riots and demonstrations occurring in 1934, 1937, 1944 and 1951.[107][108] France, having failed to quell the nationalists by deposing the popular Sultan Mohammed V and already fighting a bloody war of independence in Algeria, recognised Moroccan independence in 1956.[109]
Wikimedia Commons has media related to [[commons:Category:{{#property:P373}}|Zaian War]].
The Rif War, a 1920–26 conflict between the Rif people and the Spanish, French, and Jebala people.
↑ A tent is the traditional unit of measure for Berber tribes and holds approximately five persons.[11]
↑ The French did not expect men of the foreign legion to have to fight against their own countrymen and so Germans and Austrians, who made up 12% of the total strength of the unit in the war years, were kept away from the western front, with most serving out the war in North Africa.[34]
↑ 1.0 1.1 1.2 Trout 1969, p. 242.
↑ 2.0 2.1 2.2 2.3 Hoisington 1995, p. 65.
↑ Bidwell 1973, p. 296.
↑ 4.0 4.1 4.2 Burke 1975, p. 439.
↑ 5.0 5.1 5.2 5.3 Bimberg 1999, p. 7.
↑ Katz 2006, p. 253.
↑ Gershovich 2005, p. 100.
↑ 8.0 8.1 8.2 Bimberg 1999, p. 9.
↑ 9.0 9.1 9.2 Hoisington 1995, p. 63.
↑ Fage, Roberts & Oliver 1986, p. 290.
↑ Trout 1969, p. 78.
↑ Slavin 2001, p. 119.
↑ 13.0 13.1 Hoisington 1995, p. 59.
↑ Singer & Langdon 2004, p. 196.
↑ Bidwell 1973, p. 75.
↑ 18.0 18.1 18.2 18.3 18.4 Gershovich 2005, p. 101.
↑ 19.0 19.1 Bimberg 1999, p. 8.
↑ Hoisington 1995, p. 64.
↑ 21.0 21.1 21.2 21.3 Hoisington 1995, p. 66.
↑ 22.0 22.1 22.2 22.3 22.4 22.5 22.6 Hoisington 1995, p. 67.
↑ 24.0 24.1 24.2 24.3 24.4 24.5 24.6 24.7 Hoisington 1995, p. 70.
↑ 25.0 25.1 25.2 Bimberg 1999, p. 10.
↑ Bimberg 1999, p. 5.
↑ 30.0 30.1 30.2 Burke 1975, p. 441.
↑ 31.0 31.1 31.2 Gershovich 2005, p. 102.
↑ De Haas 2007, p. 45.
↑ Windrow 2010, p. 424.
↑ 35.0 35.1 35.2 Windrow & Chappell 1999, p. 10.
↑ Jones 2011, p. 111.
↑ 42.0 42.1 42.2 42.3 French Embassy in Morocco, Le Maroc sous domination coloniale (pdf) (in French), retrieved 29 November 2009 CS1 maint: Unrecognized language (link) <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
↑ 43.0 43.1 43.2 43.3 43.4 43.5 Bimberg 1999, p. 11.
↑ 47.0 47.1 47.2 47.3 47.4 47.5 47.6 47.7 47.8 Hoisington 1995, p. 75.
↑ Military Intelligence Division, General Staff 1925, p. 403.
↑ McDougall 2003, p. 43.
↑ 50.0 50.1 Lázaro 1988, p. 98.
↑ Jaques 2007a, p. 330.
↑ 52.0 52.1 52.2 Hoisington 1995, p. 80.
↑ 55.0 55.1 Jaques 2007c, p. 941.
↑ 56.0 56.1 56.2 56.3 56.4 56.5 Hoisington 1995, p. 83.
↑ Bimberg 1999, p. 12.
↑ 60.0 60.1 60.2 60.3 Singer & Langdon 2004, p. 207.
↑ 61.0 61.1 Windrow 2010, p. 438.
↑ 62.0 62.1 Tucker 2005, p. 726.
↑ 63.0 63.1 Woodward 1967, p. 270.
↑ 66.0 66.1 66.2 Windrow 2010, p. 442.
↑ 68.0 68.1 Jaques 2007b, p. 383.
↑ 70.0 70.1 70.2 70.3 70.4 70.5 70.6 Windrow 2010, p. 452.
↑ Burke 1975, p. 440.
↑ Lázaro 1988, p. 96.
↑ 73.0 73.1 Burke 1975, p. 444.
↑ 74.0 74.1 74.2 74.3 74.4 74.5 Burke 1975, p. 445.
↑ Strachan 2003.
↑ Pennell 2000, p. 163.
↑ Kveder, Bojan (28 June 2010), "Reviving the last Pasha of Marrakech", BBC News, retrieved 8 December 2012 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
↑ 96.0 96.1 96.2 96.3 96.4 Hoisington 1995, p. 89.
↑ 102.0 102.1 102.2 Hoisington 1995, p. 92.
↑ Trout 1969, p. 243.
↑ Segalla 2009, p. 212.
↑ Country Profile: Morocco (PDF), Library of Congress – Federal Research Division, retrieved 6 April 2013 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Bidwell, Robin Leonard (1973), Morocco Under Colonial Rule: French Administration Of Tribal Areas 1912–1956, Abingdon, UK: Frank Cass, ISBN 0-7146-2877-8 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Bimberg, Edward L. (1999), The Moroccan Goums: Tribal Warriors in a Modern War, Westport, Connecticut: Greenwood Press, ISBN 0-313-30913-2 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Lua error in Module:Citation/CS1/Identifiers at line 47: attempt to index field 'wikibase' (a nil value).
Fage, J.D.; Roberts, Andrew; Oliver, Roland Anthony (1986), The Cambridge History of Africa: From 1905 to 1940, Cambridge: Cambridge University Press, ISBN 0-521-22505-1 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Gershovich, Moshe (2005), French Military Rule in Morocco: Colonialism and its Consequences, Abingdon, UK: Frank Cass, ISBN 0-7146-4949-X <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Hoisington, William A (1995), Lyautey and the French Conquest of Morocco, New York: Macmillan (St Martin's Press), ISBN 0-312-12529-1 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Jaques, Tony (2007a), Dictionary of Battles and Sieges: A-E, Westport, Connecticut: Greenwood Press, ISBN 0-313-33537-0 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Jaques, Tony (2007b), Dictionary of Battles and Sieges: F-O, Westport, Connecticut: Greenwood Press, ISBN 0-313-33537-0 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Jaques, Tony (2007c), Dictionary of Battles and Sieges: P-Z, Westport, Connecticut: Greenwood Press, ISBN 0-313-33537-0 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Jones, Heather (2011), Violence Against Prisoners of War in the First World War: Britain, France and Germany, 1914–1920, Cambridge: Cambridge University Press, ISBN 978-0-521-11758-6 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Katz, Jonathan G. (2006), Murder in Marrakesh: Émile Mauchamp and the French Colonial Adventure, Bloomington: Indiana University Press, ISBN 0-253-34815-3 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
McDougall, James (2003), Nation, Society and Culture in North Africa, London: Frank Cass, ISBN 0-7146-5409-4 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Pennell, C.R. (2000), Morocco Since 1830: A History, London: C. Hurst & Co, ISBN 1-85065-273-2 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Segalla, Spencer D. (2009), Moroccan Soul: French Education, Colonial Ethnology, and Muslim Resistance 1912-1956, Lincoln, Nebraska: University of Nebraska Press, ISBN 978-0-8032-1778-2 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Singer, Barnett; Langdon, John W. (2004), Cultured Force: Makers and Defenders of the French Colonial Empire, Madison, Wisconsin: University of Wisconsin Press, ISBN 0-299-19900-2 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Slavin, David Henry (2001), Colonial Cinema and Imperial France, 1919–1939: White Blind Spots, Male Fantasies, Settler Myths, Baltimore, Maryland: Johns Hopkins University Press, ISBN 0-8018-6616-2 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Strachan, Hew (2003), The First World War: To Arms, Oxford: Oxford University Press, ISBN 0-19-820877-4 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Trout, Frank E. (1969), Morocco's Saharan Frontiers, Geneva: Librairie Droz, ISBN 978-2-600-04495-0 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Tucker, Spencer C. (editor) (2005), The Encyclopedia of World War One, Santa Barbara, California: ABC CLIO, ISBN 978-1-85109-420-2 CS1 maint: Extra text: authors list (link) <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Windrow, Martin; Chappell, Mike (1999), French Foreign Legion 1914–1945, Oxford: Osprey, ISBN 1-85532-761-9 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Windrow, Martin (2010), Our Friends Beneath the Sands, London: Phoenix, ISBN 978-0-7538-2856-4 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Woodward, Sir Llewellyn (1967), Great Britain and War of 1914–1918, Frome, Somerset & London: Butler & Tanner, ISBN 0-416-42400-7 <templatestyles src="Module:Citation/CS1/styles.css"></templatestyles>
Franco-Spanish conquest of Morocco (1893–1932)
French protectorate in Morocco
Spanish protectorate in Morocco
Major conflicts
Tetuan War (1859–60)
Melilla War (1893–94)
Battle of Casablanca (1908)
Battle of Sidi Bou Othman (1912)
Battle of El Herri (1914)
Battle of Annual (1921)
Moroccans
Mohammed Ameziane
Mulai Ahmed er Raisuni
Mhand n'Ifrutant
Sidi Ahmed El Hiba
Ma al-'Aynayn
Abd el-Krim
Assou Oubasslam
Aït Atta
Zayanes
Beni Ouryaghel
General Mangin
General Lyautey
General Henrys
General Poeymirau
Maréchal Pétain
Henry de Bournazel
French allies
Thami El Glaoui
Sultan Moulay Youssef
Juan García y Margallo
Martínez-Campos
Manuel Fernández Silvestre
Dámaso Berenguer
José Millán Astray
Miguel Primo de Rivera
José Sanjurjo
Generalísimo Francisco Franco
Spanish allies
Mohamed Meziane
Treaty of Fez (1894)
Algeciras Conference (1906)
Pact of Cartagena (1907)
Treaty of Fes (1912)
Franco-Spanish Treaty (1912)
First Moroccan Crisis (1905)
Agadir Crisis (1911)
History of World War I by region and country
South-West Africa
Retrieved from "https://infogalactic.com/w/index.php?title=Zaian_War&oldid=2722558"
Wars involving Morocco
Wars involving France
Berber history
Secession in Morocco
Conflicts in 1914
France–Morocco relations
20th century in Morocco
Resistance to the French colonial empire
Rebellions in Africa
1914 in Morocco
Pages with script errors
Commons category with page title different than on Wikidata

redpajama_set_name: RedPajamaCommonCrawl


text:
Rule Out DVT: Miami Cardiac & Vascular Institute Expedites Diagnoses of 'Deep Vein Thrombosis'
Written by John Fernandez
Deep vein thrombosis, better known as DVT, refers to a blood clot that forms in a deep vein. These blood clots are most common in the leg but can occur in the arm or other part of the body. In rare occasions, DVT can lead to a serious, life-threatening complication, most likely caused by a blood clot that partially or totally breaks away and travels to the lungs.
"Whenever a clinician considers the possibility of deep vein thrombosis, the patient's evaluation becomes urgent," explains Ian Del Conde, M.D., a cardiovascular specialist and director of vascular medicine at Miami Cardiac & Vascular Institute.
Because most patients with DVT require treatment with anticoagulant therapy, or blood thinners, the evaluation of patients who may have DVT has traditionally been done in the emergency room.
The Miami Cardiac & Vascular Institute created the Rule Out DVT service, which allows a patient to avoid the emergency department altogether and undergo a venous ultrasound, where a doctor at the Institute's Ambulatory Diagnostic Center can quickly confirm a DVT diagnosis.
A physician referral is needed for the ultrasound. It can come from your cardiologist, primary care physician, specialist, surgeon or oncologist. The procedure involves placing ultrasound gel on the affected area and then moving a handheld device across it. A real-time picture of the blood flow is displayed on a screen.
"The Rule Out DVT service became particularly valuable with the COVID-19 pandemic," said Dr. Del Conde. "Instead of patients being referred to the emergency room, which was often busy in caring for COVID 19 patients, patients were seen at the MCVI Ambulatory Diagnostic Center and a complete evaluation and treatment could be performed in less than 2 hours."
The Rule Out DVT service has been fully operational for months, creating a less stressful, smoother experience for patients.
"If deep vein thrombosis is diagnosed, vascular specialists onsite immediately assess the patient and start anticoagulation therapy when necessary, always discussing the case with the patient's referring doctor," says Dr. Del Conde.
What Causes Deep Vein Thrombosis?
DVT can be caused by long periods of inactivity, like too much sitting, extended bed-rest or long trips. The deep veins of the legs, located in the muscles, help carry blood to the heart. When leg muscles contract and relax, blood is squeezed through the veins back to the heart. One-way valves inside the veins help keep the blood moving in the right direction. When blood moves too slowly or not at all, it can collect (pool) in the veins. This makes a clot more likely to form.
Blood clots are becoming a symptom of some COVID-19 patients, according to various reports. In a few cases, clots are causing patients with the coronavirus to have heart attacks and strokes; form strange rashes on their skin; and develop red, swollen wounds that look like frostbite on their fingers and toes. The big takeaway is that people with underlying health conditions, including heart disease, obesity, high blood pressure and diabetes, need to be extra cautious about protecting themselves from COVID-19.
"Patients who have chronic underlying conditions still need to make sure that these conditions remain well controlled," says Dr. Del Conde. "Neglecting these conditions could represent a significant risk to the health and well-being in many patients."
Make sure to take prescribed medications and keep track of hypertension at home — if at all possible.
"Use home monitoring devices, which can be as simple as an automated blood pressure cuff or a weight scale," adds Dr. Del Conde. "Contacting a physician via telemedicine is a good way patients can stay on top of other chronic conditions and clear up any concerns or questions."
Who is Most at Risk for DVT?
Anyone can develop a blood clot. But certain factors may raise your risk for one. Anything that slows blood flow, injures the lining of a vein, or increases blood clotting can make you more likely to have DVT. You are at risk for DVT if you:
Are overweight or obese
Have a blood-clotting disorder
Are older than age 60
Had surgery
Have spent a long period of time not moving, such as staying in the hospital or traveling on a long trip
Take birth control pills or hormone replacement therapy
Are paralyzed
Are pregnant
Have a central venous catheter (for example, in a large vein in the chest)
Heart Valve Procedures in a COVID-19 World: Here are the Facts
At the height of the COVID-19 shutdown, a frail, 93-year-old man needed a complex aortic valve replacement to survive. Physicians at Miami Cardiac & Vascular Institute didn't hesitate.
'Life's Simple 7' Steps: Lowering Risk for Heart Disease More Vital Than Ever
When it comes to COVID-19, older adults with coronary heart disease or high blood pressure are more likely to develop more severe symptoms, states the American Heart Association (AHA).
For African-Americans in COVID-19 Era, Focus on Heart Health is More Vital Than Ever
New research on coronavirus patients adds to a growing collection of studies that COVID-19 disproportionately affects racial and ethnic minorities.
Quarantine Drinking: Experts Warn Against Too Many Virtual Happy Hours
With drinks like the Quarantini, many people are toasting to their colleagues and friends and de-stressing from everything COVID-19 through virtual happy hours.
Wearing Face Masks or 'Cloth Coverings' Helps Slow Spread of COVID-19
The required use of face masks could slow the spread of the coronavirus by as much as 40 percent daily, according to a new study.
A Trip to the ER During COVID-19
Sam Verdeja went to bed the night of May 14th with some discomfort in his lower left abdomen.
Meet Ken Davis: A 'Walking-Talking Miracle' After Aortic Dissection
An estimated 90 percent of people who suffer an aortic dissection die on the spot. That sobering statistic is why Ken Davis, 64, spends more time than most reflecting on his good fortune.
What You Need to Know About COVID-19 Testing
As a second wave of COVID-19 cases continues to spread across South Florida, Baptist Health is committed to caring for the community, especially those with urgent and emergent healthcare needs.


We are sorry, your password is incorrect. Please check your password and try again.
If your password is correct and you are still getting incorrect password message, please wait for 5 minutes and try again.
- if the login fails, enter the instagram application and this it was me on the button.


Supports network communication using a stream socket over TCP or Bluetooth RFCOMM in UWP apps.
The StreamSocket class supports network communications that use a stream socket over TCP or Bluetooth RFCOMM in UWP apps.
Get a StreamSocketControl object using the Control property and set any properties on the StreamSocketControl object before calling one of the ConnectAsync methods.
Call one of the ConnectAsync methods to establish a connection with the remote endpoint. For Bluetooth, the remote service name is a Bluetooth Service ID. If an SSL/TLS connection for TCP or a level of encryption for Bluetooth is required immediately, this can be specified using some of the ConnectAsync methods. If an SSL/TLS connection is desired after sending and receiving some initial data for a TCP socket, then the UpgradeToSslAsync method can be called later to upgrade the connection to use SSL.
Call the Close method to disconnect the socket, abort any pending operations, and release all unmanaged resources associated with the StreamSocket object.
Explicitly closing a StreamSocket object (calling the Close method) will ensure a graceful disconnect if no pending read or write operations exist on the socket. All pending reads are automatically aborted and the StreamSocket waits for any ongoing I/O to complete before tearing down the connection. If no unread data remains on the socket after the ongoing I/O is finished, a graceful disconnect (FIN) is guaranteed to occur. Otherwise, an ungraceful disconnect (RST) occurs.
Whenever a read or write operation is cancelled, the I/O operation completes with Error state and the associated StreamSocket object immediately tears down the connection, which leads to an ungraceful disconnect (RST) if any unread or unsent data remains on the socket.
Ungraceful disconnects (RST) will always occur if: An abnormal termination occurs (e.g., the app crashes); or an abnormal connection failure is detected by the networking stack (e.g., TCP retransmit timeout).
The StreamSocket object is also used in conjunction with the StreamSocketListener object to listen for incoming connections over TCP or Bluetooth RFCOMM in server apps or peer-to-peer apps. A StreamSocket object is returned by the Socket property on the ConnectionReceived event when a StreamSocketListener object receives a TCP or Bluetooth RFCOMM connection request. For more information, see StreamSocketListener.
In a UWP app, the StreamSocket class supports connecting to a remote endpoint when proxies are required to complete the connection. This support for proxies is automatic and transparent to the app. A StreamSocket can establish a connection through authenticating proxies as well as through other proxies where authentication is not needed. Authenticating proxies only work if Internet Explorer or an app that uses the HttpClient class in the Windows.Web.Http namespace has previously successfully authenticated with the proxy and the credentials previously used for the authentication are still valid. The support for authenticating proxies does not work if a web browser other than Internet Explorer was used to provide the authentication credentials to the proxy. Connecting through proxies is not supported if a local host address or a specific network adapter is specified on the ConnectAsync method.
In a UWP app, the ConnectAsync methods on the StreamSocket object try to discover proxies and the current proxy configuration both before and after name resolution to help speed up connection establishment. If a port is specified for the endpoint rather than a service name, both proxy discovery and name resolution are initiated internally. If proxy discovery completes before name resolution and the CanConnectDirectly property on the ProxyConfiguration object is false, then a proxy connection will be attempted. Once name resolution completes, proxy discovery is initiated again with the resolved endpoint address to determine the current proxy configuration. If CanConnectDirectly indicates after name resolution that the app can connect directly to the remote endpoint, then a socket connection will be attempted directly to the endpoint. If CanConnectDirectly is false after name resolution, then a socket connection will be attempted directly to the endpoint and a parallel socket connection is attempted through the proxy. The first connection to succeed is used by the StreamSocket and the other connection is canceled.
There may be cases where CanConnectDirectly returns false, yet it does not mean you cannot access the resource directly. A local network could be configured to have support for both a proxy and network address translation (NAT). The WPAD script used to supply proxy information to a web browser or HttpClient tells Windows that it should use the proxy. This can cause problems when the remote endpoint is not expecting a proxy connection (an HTTP CONNECT request, for example). An app can use the GetProxyConfigurationAsync method on the NetworkInformation object passing the remote endpoint and port for the uri parameter to retrieve proxy information to help determine when this condition is suspected. A way to avoid proxy connection requests from being sent when a server can only handle direct connections is to use the ConnectAsync(HostName, String, SocketProtectionLevel, NetworkAdapter) method, since the proxy-related logic is disabled when a specific network adapter is selected.
In a Windows Phone 8.x app, the StreamSocket does not provide automatic support for proxies since the ProxyConfiguration class is not supported on Windows Phone.
You must write code to handle exceptions when you call asynchronous methods on the StreamSocket class. Exceptions can result from parameter validation errors, name resolutions failures, and network errors. Exceptions from network errors (loss of connectivity, connection failures, and server failures, for example) can happen at any time. These errors result in exceptions being thrown. If not handled by your app, an exception can cause your entire app to be terminated by the runtime.
Your app can use a StreamSocket for network connections between devices that are within close range. Classes in the Windows.Networking.Proximity namespace support network connections with a StreamSocket to nearby devices that use Bluetooth or Wi-Fi Direct. The PeerFinder and related classes in the Windows.Networking.Proximity Windows.Networking.Proximity namespace let your app discover another instance of your app on a nearby device. The PeerFinder.FindAllPeersAsync method browses for peer computers that are running the same app within wireless range. The PeerFinder.ConnectAsync method returns a connected StreamSocket that your app can use to transfer network data with the nearby peer app. For more information, see Supporting proximity and tapping, Windows.Networking.Proximity, PeerFinder, and the Proximity sample.
Your app can also use a StreamSocket for network connections between devices that use Wi-Fi Direct with classes in the Windows.Devices.WiFiDirect namespace. The WiFiDirectDevice class can be used to locate other devices that have a Wi-Fi Direct (WFD) capable device. The WiFiDirectDevice.GetDeviceSelector method gets the device identifier for a nearby WFD device. Once you have a reference to a nearby WFD device, you can call the WiFiDirectDevice.GetConnectionEndpointPairs method to get an EndpointPair object. The ConnectAsync(EndpointPair) or ConnectAsync(EndpointPair, SocketProtectionLevel) method on the StreamSocket class can then be used to establish a socket connection. For more information, see Windows.Devices.WiFiDirect and WiFiDirectDevice.
Bluetooth uses Bluetooth Service IDs as endpoints for StreamSocket connections, not hostnames or IP addresses. To use a StreamSocket with Bluetooth, the bluetooth.rfcomm device capability must be set in the app manifest. For more information, see the Windows.Devices.Bluetooth.Rfcomm namespace, How to specify device capabilities for Bluetooth, and the Bluetooth Rfcomm Chat sample.
On Windows Server 2012 and Windows Server 2012 R2, the Windows.Networking.dll that implements most of the classes in the Windows.Networking.Sockets namespace will fail to load unless the Media Foundation feature is enabled. As a result, apps that use StreamSocket and related socket classes in the Windows.Networking.Sockets namespace will fail if the Media Foundation feature is disabled. Windows Server 2012 or Windows Server 2012 R2 installs with the Media Foundation feature disabled.
An app can communicate with the target DNS address that belongs to a SRV record. For example, an extensible Messaging and Presence Protocol (XMPP) service in the Contoso domain corresponds to _xmpp-client._tcp.contoso.com. That service name corresponds to a server DNS name, for example, xmpp-client01.contoso.com.
The protocol is inferred to be TCP for StreamSocket instances. The method deals with the underscore characters.
These code snippets use ConnectAsync. The GetEndpointPairsAsync method supports similar usage to connect to services.
Gets the output stream to write to the remote host on a StreamSocket object.
Starts an asynchronous operation on a StreamSocket object to connect to a remote network destination specified as an EndpointPair object.
Starts an asynchronous operation on a StreamSocket object to connect to a remote network destination specified by a remote hostname and a remote service name.
Starts an asynchronous operation on a StreamSocket object to connect to a remote destination specified by a remote hostname, a remote service name, and a SocketProtectionLevel.
Starts an asynchronous operation on a StreamSocket object on a specified local network adapter to connect to a remote destination specified by a remote hostname, a remote service name, and a SocketProtectionLevel.
Gets a list of EndpointPair objects based on a remote hostname and remote service name that can be used to send TCP packets to a remote network destination.
Gets a list of EndpointPair objects based on a remote hostname and remote service name and the sort order to be used.
Transfers ownership of the StreamSocket to the socket brokering service, which monitors socket activity and notifies the app through a background task if there is any activity.
Transfers ownership of the StreamSocket to the socket brokering service, which monitors socket activity and notifies the app through a background task if there is any activity. Specifies a new SocketActivityContext for the socket.
Transfers ownership of the StreamSocket to the socket brokering service, which monitors socket activity and notifies the app through a background task if there is any activity. Specifies a new SocketActivityContext and a keep alive time for the socket.
Starts an asynchronous operation to upgrade a connected socket to use SSL on a StreamSocket object.


Ethical clothing brand, Kowtow, has announced plans to open its first flagship store in Wellington this year.
The flagship store was set to open late 2017, but due to construction is now expected to open early of this year.
Owner and founder Gosia Piatek says more than a bit of work has gone into the initial stages of getting the building ready.
Located opposite Moore Wilsons on Collage Street, the store comes on the larger scale at 200 square-metres.
Kowtow, just passing a decade in business, has built its reputation on sustainable, ethical and transparent practises.
Influenced by architecture, street style and interior design, Kowtow has a distinctive minimalist aesthetic that is easily recognisable in New Zealand fashion press. Each item sports a notable lack of embellishments and zips.
Piatek says the new store even includes recyclable bio-degradable bags, as to comply with their ethical image.
The push back date off the opening meant Gosia and her team turned to their current space to offer customers a place to shop exclusively in their range.
Winter season will be available instore at the opening, including Kowtows new merino ware range.


When you are building a new home you naturally want to use the best quality materials. This is not only for aesthetic purposes, but when your home contains cheap materials that are of an inferior quality they are more than liable to deteriorating over time, often not a very long time.
QSTONE is manufactured with incredibly high quartz for use in home and commercial property buildings. Using a combination of quartz and advanced resin, it creates a product that when used has stain and wear resistant properties.
Whilst selecting natural marble for a property is a great idea for its aesthetic, the raw material does not stand up well against the test of time and easily stains. People often purchase the material for their kitchen benchtops and as soon as a glass of wine or stray drop of beetroot liquid hits the top can stain the surface. QSTONE is a quartz product that whilst retaining the beauty and opulent design of marble, is far more durable. Our product consists of 94% quartz and 6% advanced resin, with the binding agent creating a quality of material that will last.
Our quartz is resistant to impact, corrosive materials, cracking and scratches.
Quartz is perfect for kitchen benches and splashbacks, as it is resistant to the products you would find in an everyday home. Nail polish and food dyes? No problem. It's not going to stain this benchtop. Also resistant to fruit juice, markers, coffee and wine.
Our beautiful quartz comes in a fantastic array of colours and styles. From Diamond White to Steel Grey, Oyster Pearl to Belgium Black. Whatever style or aesthetic you are going for, QSTONE has you covered with an extensive catalogue of fine quartz. Style and opulence combined with quality and durability, this is what we strive to create at Q Stone.
Like the sound of using our high-quality product for your new home build? Simply get in touch with the team at JH Wilberforce on (08) 9340 6222 or by filling out an enquiry form on our contact page and we will happily assist you with your enquiries.
Quartz choice For Kitchen Renovations!
Luxurious Marble Look for Quality Shenton Park Residence.


The Professional Regulation Commission (PRC) announces that 3,616 out of 14,358 passed the Certified Public Accountant Licensure Examination given by the Board of Accountancy in the cities of Manila, Baguio, Cagayan De Oro, Cebu, Davao, Iloilo, Legazpi, Lucena, Tacloban and Tuguegarao this October 2018. The results of examination with respect to three (3) examinees were withheld pending final determination of their liabilities under the rules and regulations governing licensure examination.
From October 29 to November 13, 2018, registration for the issuance of Professional Identification Card (ID) and Certificate of Registration will be done on-line. Please go to www.prc.gov.ph and follow instructions for initial registration. Those who will register are required to bring the following: downloaded duly accomplished Oath Form or Panunumpa ng Propesyonal, notice of admission (for identification only), 2 pieces passport sized pictures (colored with white background and complete name tag), 2 sets of documentary stamps and 1 piece short brown envelope. Successful examinees should personally register and sign in the Roster of Registered Professionals.


text:
Your digital HQ
Sign inTalk to salesTry for free
Sign inDownload Slack
Close navigationClose navigation
Slack API Terms of Service
Additional Terms PagesClose legal navigation
Customer terms of service
User terms of service
Customer-specific suppl.
App Directory agreement
GovSlack service level agreement
Data processing addenda
Slack Partner Programme terms and conditions
Slack brand terms of service
Slack subprocessors
Slack affiliates
Multi-year accessibility subscription
Slack Certified programme
Slack Certified Participant Agreement
Slack Community Forum terms of service
Terms and policy archives
Effective: 14th September 2022
These Slack API Terms of Service (the 'API Terms') describe your rights and responsibilities when accessing our application programming interfaces, software development kits, sample code, command line tools, developer tools and other related documentation and materials made available by Slack, including, without limitation, through the Slack API website (collectively, 'APIs'). Please read them carefully. We're grateful that you're here.
Relationships and definitions
These API Terms, together with the Slack Application Developer Policy form a binding 'Contract' between you and us. 'We', 'our' and 'us' refer to the applicable Slack entity in the section entitled 'Which Slack entity are you contracting with?' below, and 'you' and 'your' refer to the individual, company or legal entity that you represent. The Contract does not grant you any right to access or use our online workplace productivity tools and platform (the 'Services'), which will be governed by a separate agreement with us (e.g. our Customer Terms of Service).
The Slack Extended Family
We may leverage our employees, those of our corporate affiliates and third party contractors (the 'Slack Extended Family') in exercising our rights and performing our obligations under the Contract. We will be responsible for the Slack Extended Family's compliance with our obligations under the Contract.
Access to our APIs
Subject to the restrictions below, we grant you a non-exclusive, worldwide, non-transferable (subject to the section titled 'Assignment'), limited license to access our APIs only as necessary to develop, test, use and support an application (an 'Application' or 'App') with the Services. You may charge for your Application; however, you may not sell, rent, lease, sublicense, redistribute or syndicate access to any of our APIs.
Here are the rules:
Your license to access our APIs is limited and subject to compliance with the Slack Application Developer Policy and Slack's Brand Guidelines. You must use the APIs only in accordance with this Contract and comply with the acceptable use policy. Further, you will not: (A) access our APIs in violation of any law or regulation; (B) access our APIs in any manner that (i) compromises, breaks or circumvents any of our technical processes or security measures associated with the Services, (ii) poses a security vulnerability to customers or users of the Services or (iii) tests the vulnerability of our systems or networks; (C) access our APIs in order to replicate or compete with the Services; (D) attempt to reverse-engineer or otherwise derive source code, trade secrets or know-how of our APIs or Services; or (E) attempt to use our APIs in a manner that exceeds rate limits, or constitutes excessive or abusive usage.
Transparency and reporting
If you offer your application for use by others outside your organisation, you must maintain a user agreement and privacy policy for your application, which is prominently identified or located where users download or access your application. Your privacy policy must meet applicable legal standards and describe the collection, use, storage and sharing of data in clear, understandable and accurate terms. You are required to follow applicable legal requirements if the use of your app will result in the international transfer of personal data. You must promptly notify us in writing via email to security@slack.com of any breaches of your user agreement or privacy policy that impact or may impact customers or users of the Services. Please review our Privacy Policy for more information on how we collect and use data relating to the use and performance of our websites and products.
Our right to suspend access and audit
If we believe that there is a violation of the Contract that can simply be remedied by your modification or update of your Application, we will, in most cases, ask you to take direct action rather than intervene. In such instance, we may use your name, address and other contact details to contact you or provide this contact information to any third party that reasonably, in Slack's sole determination, claims that you do not possess all of the necessary intellectual property rights. In some instances, we may directly step in and take what we determine to be appropriate action if you are not responsive, or if we believe there is a credible risk of harm to us, the Services, our customers or users or any third parties. Slack also reserves a right to audit your application to ensure it does not violate our terms and policies. You agree that you will cooperate with inquiries related to such an audit and provide us with proof that your application complies with our terms and policies.
Ownership and proprietary rights
You retain your ownership rights in your Application and we own and will continue to own our APIs and Services, including all related intellectual property rights therein. All of our rights not expressly granted by the Contract are hereby retained.
The more suggestions our developers make, the better our APIs become. If you send us any feedback or suggestions regarding the APIs, there is a chance we will use them, so you grant us an unlimited, irrevocable, perpetual, sublicensable, transferable, royalty-free license to use any such feedback or suggestions for any purpose without any obligation or compensation to you. If we choose not to implement the suggestion, please don't take it personally. We appreciate it nonetheless.
Each party ('Disclosing Party') may disclose 'Confidential Information' to the other party ('Receiving Party') in connection with the Contract, which is anything that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure including non-public business, product, technology and marketing information. If something is labelled 'Confidential', that is a clear indicator to the Receiving Party that the material is confidential. Notwithstanding the above, Confidential Information does not include information that (a) is or becomes generally available to the public without breach of any obligation owed to the Disclosing Party; (b) was known to the Receiving Party prior to its disclosure by the Disclosing Party without breach of any obligation owed to the Disclosing Party; (c) is received from a third party without breach of any obligation owed to the Disclosing Party; or (d) was independently developed by the Receiving Party.
Protection and use of Confidential Information
The Receiving Party will (a) take at least reasonable measures to prevent the unauthorised disclosure or use of Confidential Information, and limit access to those employees, affiliates and contractors who need to know such information in connection with the Contract; and (b) not use or disclose any Confidential Information of the Disclosing Party for any purpose outside the scope of this Contract. Nothing above will prevent either party from sharing Confidential Information with financial and legal advisors; provided, however, that the advisors are bound to confidentiality obligations at least as restrictive as those in the Contract.
Compelled access or disclosure
The Receiving Party may access or disclose Confidential Information of the Disclosing Party if it is required by law; provided, however, that the Receiving Party gives the Disclosing Party prior notice of the compelled access or disclosure (to the extent legally permitted) and reasonable assistance, at the Disclosing Party's cost, if the Disclosing Party wishes to contest the access or disclosure. If the Receiving Party is compelled by law to access or disclose the Disclosing Party's Confidential Information, the Disclosing Party will reimburse the Receiving Party for its reasonable cost of compiling and providing access to such Confidential Information as well as the reasonable cost for any support provided in connection with the Disclosing Party seeking a protective order or confidential treatment for the Confidential Information to be produced.
You may terminate the Contract by discontinuing use of our APIs. We may terminate the Contract with or without cause, and without notice to you. Upon termination of the Contract, all rights and licenses granted to you will terminate immediately. You understand that any APIs that are not made generally available but that are otherwise made available to you are the confidential information of Slack. Upon termination of the Contract, you will promptly destroy copies of any documentation and any other Slack information in your possession or control that was received under the Contract.
Representations; Disclaimer of Warranties
You represent and warrant that you have validly entered into the Contract and have the legal power to do so.
EXCEPT AS EXPRESSLY PROVIDED FOR HEREIN, THE APIS AND ALL RELATED COMPONENTS AND INFORMATION ARE PROVIDED BY US ON AN 'AS IS' AND 'AS AVAILABLE' BASIS WITHOUT ANY WARRANTIES OF ANY KIND, AND WE EXPRESSLY DISCLAIM ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, TITLE, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. YOU ACKNOWLEDGE THAT WE DO NOT WARRANT THAT THE APIS WILL BE UNINTERRUPTED, TIMELY, SECURE OR ERROR-FREE.
IN NO EVENT WILL OUR OR THE SLACK EXTENDED FAMILY'S AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THE CONTRACT (WHETHER IN CONTRACT OR TORT OR UNDER ANY OTHER THEORY OF LIABILITY) EXCEED US$100.
IN NO EVENT WILL WE OR THE SLACK EXTENDED FAMILY HAVE ANY LIABILITY TO YOU OR TO ANY THIRD PARTY FOR ANY LOST PROFITS OR REVENUES OR FOR ANY INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, COVER OR PUNITIVE DAMAGES HOWEVER CAUSED, WHETHER IN CONTRACT, TORT OR UNDER ANY OTHER THEORY OF LIABILITY, AND WHETHER OR NOT YOU OR THE THIRD PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING DISCLAIMER WILL NOT APPLY TO THE EXTENT PROHIBITED BY APPLICABLE LAW.
The limitations under this 'Limitation of Liability' section apply with respect to all legal theories, whether in contract, tort or otherwise, and to the extent permitted by law. The provisions of this 'Limitation of Liability' section allocate the risks under the Contract between the parties, and the parties have relied on these limitations in determining whether to enter into the Contract.
Application of consumer law
Our APIs are intended for use by businesses and organisations and not for consumer purposes. To the maximum extent permitted by law, you hereby acknowledge and agree that consumer laws do not apply. If, however, any consumer laws (e.g. in Australia, the Competition and Consumer Act 2010 (Cth)) do apply and cannot otherwise be lawfully excluded, nothing in these API Terms will restrict, exclude or modify any statutory warranties, guarantees, rights or remedies that you have, and our liability is limited (at our option) to the replacement or repair of the APIs.
Your indemnification of Us
You will defend us and the members of the Slack Extended Family (collectively, the 'Slack Indemnified Parties') from and against any and all third-party claims, actions, suits, proceedings and demands arising from or related to your violation of the Contract or your violation of your user agreement or privacy policy (a 'Claim Against Us'), and will indemnify the Slack Indemnified Parties for all reasonable solicitor's fees incurred and damages and other costs finally awarded against a Slack Indemnified Party in connection with or as a result of, and for amounts paid by a Slack Indemnified Party under a settlement you approve of in connection with, a Claim Against Us. We must provide you with prompt written notice of any Claim Against Us and allow you the right to assume the exclusive defence and control, and cooperate with any reasonable requests assisting your defence and settlement of such matter. This section states your sole liability with respect to, and the Slack Indemnified Parties' exclusive remedy against you for, any Claim Against Us.
Limitations on indemnifications
Notwithstanding anything contained in the preceding section, (a) we will always be free to choose our own counsel if we pay for the cost of such counsel; and (b) no settlement may be entered into by you, without our express written consent (such consent not to be unreasonably withheld), if: (i) the third party asserting the claim is a government agency, (ii) the settlement arguably involves the making of admissions, (iii) the settlement does not include a full release of liability, or (iv) the settlement includes terms other than a full release of liability and the payment of money.
The sections titled 'Our rights to suspend access and audit', 'Ownership and proprietary rights', 'Confidentiality', 'Termination', 'Representations; Disclaimer of warranties', 'Limitation of liability', 'Your indemnification of us', 'Limitations on indemnifications' and 'Survival', as well as all of the provisions under the general heading 'General provisions', will survive any termination or expiration of the Contract.
You grant us the right to use your company name and logo as a reference for marketing or promotional purposes on our website and in other public or private communications with our existing or potential developers and customers, subject to your standard trademark usage guidelines as provided to us from time-to-time.
Neither we nor you will be liable by reason of any failure or delay in the performance of its obligations on account of events beyond the reasonable control of a party, which may include denial-of-service attacks, a failure by a third-party hosting provider or utility provider, strikes, shortages, riots, fires, acts of God, war, terrorism and governmental action.
Relationship of the parties; no third-party beneficiaries
The parties are independent contractors. The Contract does not create a partnership, franchise, joint venture, agency, fiduciary or employment relationship between the parties. There are no third-party beneficiaries to the Contract.
Emails and Slack messages
Except as otherwise set forth herein, all notices under the Contract will be by email, although if you have a Services account, we may instead choose to provide notice to you through the Services (e.g., a Slackbot notification). Notices to Slack will be sent to feedback@slack.com, except for legal notices, such as notices of termination, which must be sent to legal@slack.com. Notices will be deemed to have been duly given (a) the day after they are sent, in the case of notices through email; and (b) the same day, in the case of notices through the Services.
Export controls and sanctions
Applications made available on the Slack platform may be subject to United States' and other jurisdictions' export control and sanctions laws and regulations. You agree to comply strictly with all such export control and sanctions laws and regulations that apply to your distribution or use of the APIs and Applications, including, but not limited to, requirements in the Slack Application Developer Policy.
Modifications to our APIs
Slack is still evolving, and so we need the flexibility to occasionally make changes to our APIs, including backwards incompatible changes. We will try to give notice of these changes, but you should consider following the @slackapi Twitter account or viewing our changelogs for updates. Also, parts of our APIs are undocumented, including certain methods, events and properties. Given that these undocumented aspects of our APIs may change at any time, you should not rely on their behaviours.
Modifications to the contract
As our business evolves, we may change these API terms and the other components of the Contract. If we make a material change to the Contract, we will provide you with reasonable notice prior to the change taking effect, either by emailing the email address associated with your account or by messaging you through the Services. You can review the most current version of the API Terms at any time by visiting this page and by visiting the most current versions of the other pages that are referenced in the Contract. The materially revised Contract will become effective on the date set forth in our notice, and all other changes will become effective upon posting of the change. If you access our APIs after the effective date, that access will constitute your acceptance of any revised terms and conditions.
No failure or delay by either party in exercising any right under the Contract will constitute a waiver of that right. No waiver under the Contract will be effective unless made in writing and signed by an authorised representative of the party being deemed to have granted the waiver.
The Contract will be enforced to the fullest extent permitted under applicable law. If any provision of the Contract is held by a court of competent jurisdiction to be contrary to law, the provision will be modified by the court and interpreted so as best to accomplish the objectives of the original provision to the fullest extent permitted by law, and the remaining provisions of the Contract will remain in effect.
Neither party may assign or delegate any of its rights or obligations hereunder, whether by operation of law or otherwise, without the prior written consent of the other party (not to be unreasonably withheld). Notwithstanding the foregoing, either party may assign the Contract in its entirety, without consent of the other party, to a corporate affiliate or in connection with a merger, acquisition, corporate reorganisation or sale of all or substantially all of its assets. Any purported assignment in violation of this section is void. A party's sole remedy for any purported assignment by the other party in breach of this section will be, at the non-assigning party's election, termination of the Contract upon written notice to the assigning party. Subject to the foregoing, the Contract will bind and inure to the benefit of the parties, their respective successors and permitted assigns.
Which Slack entity are you contracting with?
All references to 'Slack', 'we' or 'us' under the Contract, what law will apply in any dispute or lawsuit arising out of or in connection with the Contract, and which courts have jurisdiction over any such dispute or lawsuit, depend on where you are domiciled.
Slack contracting entity
Slack Technologies, LLC
San Francisco County, California
Slack Technologies Limited
The Contract, and any disputes arising out of or related hereto, will be governed exclusively by the applicable governing law above, without regard to conflicts of laws, rules or the United Nations Convention on the International Sale of Goods. The courts located in the applicable venue above will have exclusive jurisdiction to adjudicate any dispute arising out of or relating to the Contract or its formation, interpretation or enforcement. Each party hereby consents and submits to the exclusive jurisdiction of such courts. Each party also hereby waives any right to jury trial in connection with any action or litigation in any way arising out of or related to the Contract. In any action or proceeding to enforce rights under the Contract, the prevailing party will be entitled to recover its reasonable costs and solicitor's fees.
The Contract, including these API terms constitutes the entire agreement between the parties and supersedes all prior and contemporaneous agreements, proposals or representations, written or oral, concerning its subject matter. To the extent of any conflict or inconsistency between the provisions in these API Terms and any other documents or pages referenced in these API Terms, the following order of precedence will apply: (A) the API Terms, (B) Slack Application Developer Policy and (C) any other documents or pages referenced in the Contract.
Try Slack with your team for free
Why Slack?
Slack vs email
Paid vs free
Selecting a different region will change the language and content of slack.com.
©2023 Slack Technologies, LLC, a Salesforce company. All rights reserved. Various trademarks held by their respective owners.