After a long wait, proceedings against
@advocatemahere finally commence in Courtroom No. 11 before Magistrate Utahwashe.

David Drury tells Magistrate Utahwashe that the State can't make a "Lazarus" resurrection to a law which is non-existent.
Prosecutor Muchemwa tells Magistrate Utahwashe that the State is sticking to allegations contained in the charge sheet and applies for @advocatemahere to be placed on remand.
@advocatemahere's lawyers challenge State bid to place her on remand.
Drury says he is interested in knowing the identity of the woman who was allegedly roughed up by @PoliceZimbabwe.
Drury tells Magistrate Utahwashe that there is nothing illegal about @advocatemahere tweets.
In strange submissions, Prosecutor Muchemwa says section 20 of the former Constitution is worded differently with section 61 of the current Constitution hence section 31 (a)(i) & section 31(a)(iii) is still valid.
Magistrate Utahwashe orders State to investigate complaints raised by @advocatemahere & furnish court with a report by Friday 15 January 2021.
Advocate Mahere will spend 3 days in prison custody to Friday when Magistrate Utahwashe will hand down his ruling on her application challenging state bid to place her on remand.

More from Legal

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.