The chart-topping band of @ChrisGiles_ @jimbrunsden (me on drums) have a piece up about the Brexit level playing field stand-off. But here's the thing: the opacity surrounding these (as so many) trade talks is making things much worse. Quick 🧵

One of the things that struck me talking to experts about this was a lot of hedging about "this is what I think the EU means" and "this is what the UK appears to believe". There's lots of jargon (non-regression, ratchet, equivalence etc) capable of multiple meanings. (2/n)
And even if the negotiators have been clear with each other about what they mean, they certainly aren't being transparent with their domestic constituencies: the EU member states and Westminster MPs aren't being given full details about exactly what's being proposed. (3/n)
There's an unhelpful culture of secrecy around almost all trade talks. Few texts are released along the way. The standard reason is so not to give away negotiating positions to the other side. This is, to use a technical WTO term, obvious bollocks. (4/n) https://t.co/95Qp5ugHIo
If you're not telling the other side what you're proposing, you aren't negotiating, are you? Duh. The function of secrecy is actually to hide from the public what's going on. But how are you supposed to build domestic consensus around a proposal no-one can see? (5/n)
On Monday I wrote about the possibility of rational failure in the talks. It's quite possible eg Boris Johnson is failing to tell the British public about what UK & EU are really proposing because he wants no-deal. OK, that's his choice. He's PM. https://t.co/A4gMXUoOxt (6/n)
But it's also possible that a feasible landing zone is missed because both sides are genuinely unaware what their domestic constituencies (France, the ERG) will accept. (7/n)
And unless you drag these proposals into daylight and let us all work out exactly what we are talking about, the chance for mishap will increase. Might it mean the talks immediately die, as there clearly is no chance of the red lines intersecting? Maybe. (8/n)
But at this rate, unless this whole stand-off is carefully choreographed (a real possibility btw) they're heading for failure anyway. Might as well give transparency a go. When all else fails, try telling the truth. You never know, it might work. (9/9)

More from Brexit

A further thread on the EU/UK musicians/visa for paid work issue (the issue is paid work: travelling to sing or play at eg a charity event for free can be done without a visa).


The position that we now have now (no relevant provisions under the TCA) is complicated. For EU musicians visiting the UK see


In essence the UK permits foreign (including EU) nationals to stay up to 30 days to carry out paid engagements, but they must (a) prove they are a professional musician and (b) be invited by an established UK business.

Either condition could be tricky for a young musician starting out and wanting to play gigs. And 30 days isn’t long enough for a part in a show with a run.

Longer stays require a T5 visa - which generally requires you to be in a shortage occupation (play an instrument not played in the UK?) or to have an established international reputation.

You May Also Like

The UN just voted to condemn Israel 9 times, and the rest of the world 0.

View the resolutions and voting results here:

The resolution titled "The occupied Syrian Golan," which condemns Israel for "repressive measures" against Syrian citizens in the Golan Heights, was adopted by a vote of 151 - 2 - 14.

Israel and the U.S. voted 'No'
https://t.co/HoO7oz0dwr


The resolution titled "Israeli practices affecting the human rights of the Palestinian people..." was adopted by a vote of 153 - 6 - 9.

Australia, Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No' https://t.co/1Ntpi7Vqab


The resolution titled "Israeli settlements in the Occupied Palestinian Territory, including East Jerusalem, and the occupied Syrian Golan" was adopted by a vote of 153 – 5 – 10.

Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No'
https://t.co/REumYgyRuF


The resolution titled "Applicability of the Geneva Convention... to the
Occupied Palestinian Territory..." was adopted by a vote of 154 - 5 - 8.

Canada, Israel, Marshall Islands, Micronesia, and the U.S. voted 'No'
https://t.co/xDAeS9K1kW
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.