Thread day after @MyMDC_T held its Ex congress @DrThoko_Khupe chaired an alleged National council, which arrived at the resolution of firing @DMwonzora recall him from parliament. The resolutions were supposed to be read by #Phugeni then party spokesperson but he refused ...
28 Dec 2020
Upholding and Respecting the Supreme Court Judgment (SC56/2020) which ordered the holding of an EO C in terms of the party constitution to elect a substantive replacement for the late Party President Dr Morgan Richard Tsvangirai.
Affirming that the Supreme Court judgement doesn’t entail deviating from the clear provisions of our constitution.
Acknowledging the resolutions of the N Cof 9 May 2020, which meeting resolved to
(ii) . go for the ordered EO Congress in line with the party constitution
(iii) recall those elected members, in parliament and local government, who have chosen to join or support or form other political parties.
Reiterates its adherence to its
Pursuant to the Supreme Court Judgement SC56/2020 this National Council resolves the following;
3. That the party’s legal teams look into the issue of the 31st Dec deadline imposed by the S C variation in view of the 27 Dec charade.
More from News
Terry Yumbulul didn’t write the letter and didn’t agree with its content. He said so himself in a video published the next day https://t.co/IJ6ricZeRi and in a written statement published later the same day
The weird thing was, it soon emerged that large sections of the letter had been cribbed from other sources. Weird because as a Yolngu lawman, Terry didn’t need to borrow his knowledge from unrelated, alternate sources ... pretty much verbatim
The fallout was swift. Bolt was compelled to do a correction on his column and Cashman was just as swiftly dumped from her position of the Morrison government’s Senior Advisory Group for an Indigenous Voice to Government
There was no apology from either of them or from NewsCorp tho, and with the assistance of Sky News After Dark they desperately attempted to obfuscate the reality that everybody involved had been caught out and left red faced
You May Also Like
These setups I found from the following 4 accounts:
1. @Pathik_Trader
2. @sourabhsiso19
3. @ITRADE191
4. @DillikiBiili
Share for the benefit of everyone.
Here are the setups from @Pathik_Trader Sir first.
1. Open Drive (Intraday Setup explained)
#OpenDrive#intradaySetup
— Pathik (@Pathik_Trader) April 16, 2019
Sharing one high probability trending setup for intraday.
Few conditions needs to be met
1. Opening should be above/below previous day high/low for buy/sell setup.
2. Open=low (for buy)
Open=high (for sell)
(1/n)
Bactesting results of Open Drive
Already explained strategy of #opendrive
— Pathik (@Pathik_Trader) May 27, 2020
Backtested results in 30 stocks and nifty, banknifty.
Success ratio : approx 40-45%
RR average 1:2
Entry as per strategy
Stoploss = Open level
Exit 3:15 PM Or SL
39 months 14 months -ve, 25 +ve
Yearly all 4 years +ve performance. pic.twitter.com/nGqhzMKGVy
2. Two Price Action setups to get good long side trade for intraday.
1. PDC Acts as Support
2. PDH Acts as
So today we will discuss two more price action setups to get good long side trade for intraday.
— Pathik (@Pathik_Trader) June 20, 2020
1. PDC Acts as Support
2. PDH Acts as Support
Example of PDC/PDH Setup given
#nifty
— Pathik (@Pathik_Trader) June 23, 2020
This is how it created long setup by taking support at PDC.
hopefully shared setup on last weekend helped. pic.twitter.com/2mduSUpMn5
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.