This is a thread about how Australia has become the battleground for a power struggle between governments and Big Tech, as explained in today’s Download newsletter. https://t.co/BJ7uxYhoIl

Australians woke up on Thursday to Facebook timelines devoid of any news.
Faced with the option of either paying to link back to publishers to comply with an incoming Australian law, or entirely pulling the plug on hosting news, it chose the latter.
As it stands, Facebook users in Australia can't use the platform to see or share content from any news outlets anywhere in the world, and no one can post links to Australian publishers, wherever they are.
Users say government websites like fire services and meteorology departments have been caught up in the ban too, most likely due to issues with the machine learning
system Facebook uses to enforce it.

https://t.co/03E4wNy3tp

https://t.co/VamKEewZPH
Users and officials in Australia reacted furiously, with the country's prime minister, @ScottMorrisonMP, describing Facebook's actions "as arrogant as they were disappointing" and insisting "we will not be intimidated by Big Tech." https://t.co/q1Fxa7ZSdI
Why? Lawmakers are in the final stages of passing a proposed new Media Bargaining law. The law would require the tech platforms to have to pay publishers to host their content. If they couldn’t agree a price, Australia would create an arbitration panel which would set one.
Google has taken the opposite approach to Facebook, and has cut numerous deals with publishers in Australia, including @newscorpaus, to ensure it can comply with the law if it passes, and continue linking to their services. https://t.co/UQSXclYQMt
What's next? Australia has essentially become the latest battleground for the years-long fight between governments, publishers, and Big Tech.
Facebook's move is a big, ugly power flex, but Australia's law seems pretty crude and unattractive too. https://t.co/TYOv2nhzUm
Facebook’s move doesn't require publishers to plough any of the money they receive into journalists' salaries or original reporting, and could help to further entrench Australia's already highly concentrated media market.
In short, the current situation is unsustainable and undesirable for everyone.
Australia’s Treasurer @JoshFrydenberg is in talks with Facebook's CEO Mark Zuckerberg, and the pressure is on for them to come up with a better solution.
(1/2) Here's some additional reading via @platformer and @CaseyNewton: https://t.co/lrZ4TKaPC1
(2/2) As well as the @nytimes: https://t.co/v6MS6F7YKH
This analysis was originally written by @charlottejee for The Download newsletter, your daily dose of what’s up in emerging technology. You can read today’s edition here: https://t.co/BJ7uxYhoIl
Want to receive The Download in your inbox every weekday. SIGN UP here (it’s free): https://t.co/X5uDXExwrd

More from World

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.