1 So, today we turn to early Islamic Beirut. what do we know of the earliest times of #Beirut under early Islamic rule, starting with the #conquest. How and when did Beirut enter the emerging Muslim empire? -rm
More from Tweeting Historians
I want to talk about the key textual elements you might find in an Islamic manuscript. I'll focus on this manuscript, roughly 18th century, of an Arabic history of the rulers of Egypt called Nuzhat al-nāẓirīn, by Marʻī al-Karmī (d. 1623/4).
Budeiry Library (Jerusalem) MS 593 -jm
These texts have many elements designed to help the reader understand what they're saying, and choices by the scribe who copied the manuscript often help as well. Let's see what's here. -jm
First, almost every Islamic text begins with the invocation "in the name of God, the compassionate, the merciful." The wording is never changed, and it's always in Arabic, no matter what language the text is, although you might add phrases like "and we ask God for help." -jm
Christians were able to do more experimentation with their invocations, as you can see from the examples here. https://t.co/wEPWRitCWA -jm
After the invocation (basmalah), you might have what this text has, which is an introduction of the author in the form "the poor slave of God [so-and-so] said..." often followed by a quick prayer for the author. -jm
Budeiry Library (Jerusalem) MS 593 -jm
These texts have many elements designed to help the reader understand what they're saying, and choices by the scribe who copied the manuscript often help as well. Let's see what's here. -jm
First, almost every Islamic text begins with the invocation "in the name of God, the compassionate, the merciful." The wording is never changed, and it's always in Arabic, no matter what language the text is, although you might add phrases like "and we ask God for help." -jm
Christians were able to do more experimentation with their invocations, as you can see from the examples here. https://t.co/wEPWRitCWA -jm
These little prayers are fun pic.twitter.com/hJYk2M01bO
— Josh Mugler (@J_mugs) February 16, 2019
After the invocation (basmalah), you might have what this text has, which is an introduction of the author in the form "the poor slave of God [so-and-so] said..." often followed by a quick prayer for the author. -jm
More from World
I'll bite, Mr. Gray. We can even play by your rather finicky rules.
Let's begin with some of the things you have said about Xinjiang, notably absent from your more recent media appearances, but still present in your blog about your 2014 biking trip.
The following is taken from an ongoing list I keep of people who have been to Xinjiang and written/spoken about their experiences. It is separate from the testimony of detainees and their relatives I also keep. Jerry is on this
Jerry, your article for CGTN, as well as your various Medium pieces, belabor themselves to emphasize the smoothness of your time in Xinjiang. Why did you leave out so many details from your log of your 2014 trip? They seem relevant.
For example, would CGTN not let you speak about Shanshan, the town that evidently disturbed you so much?
Why, pray tell, after noting how kind and hospitable Xinjiang police were to you in 2019 for CGTN—and how you were never told where you could or could not go—would you omit these details?
Let's begin with some of the things you have said about Xinjiang, notably absent from your more recent media appearances, but still present in your blog about your 2014 biking trip.
Prove it...
— Jerry's China (@Jerry_grey2002) December 30, 2020
Without quoting Adrian Zenz who's never been there or exiles and criminals who seek asylum or cash for their stories or perhaps some satellite images of shopping centres and factories with fencelines.
You can't show any evidence that this is true https://t.co/wiozJIjusH
The following is taken from an ongoing list I keep of people who have been to Xinjiang and written/spoken about their experiences. It is separate from the testimony of detainees and their relatives I also keep. Jerry is on this
Jerry, your article for CGTN, as well as your various Medium pieces, belabor themselves to emphasize the smoothness of your time in Xinjiang. Why did you leave out so many details from your log of your 2014 trip? They seem relevant.
For example, would CGTN not let you speak about Shanshan, the town that evidently disturbed you so much?
Why, pray tell, after noting how kind and hospitable Xinjiang police were to you in 2019 for CGTN—and how you were never told where you could or could not go—would you omit these details?
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.