The numbers on their face for the @FCC RDOF auction are exciting - lots of Gigabit winners. But it’s important to remember the job is just starting. These rural areas don’t magically get Gig today or tomorrow. 1/

The job is only done and the celebration can really only begin once we see that rural Americans are actually going to get the broadband they’ve been promised. 2/
And that’s the rub here - at least from preliminary indications, there are LOTS of question marks clearly hanging out there once you look past the gloss and proclamations. And since we won’t know for maybe 5 years if it worked, due diligence is essential now. 3/
A number of big winners have offered some service but never done Gig. This would be like giving hundreds of millions of $ to firms that have repaved residential streets to now design & build our interstate highway bridges. 4/
A number of big winners are using tech that has done Gig (maybe) only in tightly controlled applications that don’t look anything like rural America. This would be like giving interstate highway $ to firms who’ve built lots of scale models but never actually built a bridge. 5/
Some winners have never offered commercial service &/or are using tech tested sparingly & selectively. This would be like awarding hundreds of millions of $ for interstate highway bridges to a firm that has developed a new concrete mix tested in a few driveways so far. 6/
Maybe some or all of these folks can do it, but there’s no transparency into how it was determined that they can do so - and the effective “waivers” given to them to be able to bid at this level were awarded behind closed doors without any public process or transparency. 7/
And now, unfortunately, bouncing any of the applications would be tantamount to declaring the auction a failure in that area - so that seems unlikely to happen. And, yet again, the public will not be able to see if these applications show the capability to perform. 8/
So in short, we are staking the future of rural voice & broadband in these areas on behind the scenes review of untested technologies - and we will only find out if that “predictive judgment” worked/failed after years have passed and hundreds of millions of $ are spent. 9/
More specifically, it will take several years to build these networks & a year or two more before they have to test. Without better betting, we therefore might not find out where predictions & hopes fell down - where this auction failed - until 2025 or later. 10/
We are all hoping that every customer who has been promised broadband gets it. But a “trust us - this will work” set of promises reviewed only behind closed doors isn’t terribly reassuring. Many of these areas have already been burned once by overpromises and underdelivery. 11/
Transparency and accountability should be hallmarks of broadband funding policy. @NTCAconnect specifically urged before the auction for much more upfront from bidders of all kinds - incl. our members! - and to make the process for review more public. 12/
Neither happened, so the only hope now is that the FCC’s back-end review (also confidential) is truly stringent - because if it’s not, a lot of Americans may be left waiting for service and we won’t find out that once again the process failed them until it’s far too late. 13/
It’s not too late to get this right by vetting winners in a more transparent and accountable way before $ flow. But it’s way too important to not do that when billions of $ and millions of customers are in the balance. #AimHigherDoBetter 14/

More from Society

You May Also Like

🌿𝑻𝒉𝒆 𝒔𝒕𝒐𝒓𝒚 𝒐𝒇 𝒂 𝑺𝒕𝒂𝒓 : 𝑫𝒉𝒓𝒖𝒗𝒂 & 𝑽𝒊𝒔𝒉𝒏𝒖

Once upon a time there was a Raja named Uttānapāda born of Svayambhuva Manu,1st man on earth.He had 2 beautiful wives - Suniti & Suruchi & two sons were born of them Dhruva & Uttama respectively.
#talesofkrishna https://t.co/E85MTPkF9W


Now Suniti was the daughter of a tribal chief while Suruchi was the daughter of a rich king. Hence Suruchi was always favored the most by Raja while Suniti was ignored. But while Suniti was gentle & kind hearted by nature Suruchi was venomous inside.
#KrishnaLeela


The story is of a time when ideally the eldest son of the king becomes the heir to the throne. Hence the sinhasan of the Raja belonged to Dhruva.This is why Suruchi who was the 2nd wife nourished poison in her heart for Dhruva as she knew her son will never get the throne.


One day when Dhruva was just 5 years old he went on to sit on his father's lap. Suruchi, the jealous queen, got enraged and shoved him away from Raja as she never wanted Raja to shower Dhruva with his fatherly affection.


Dhruva protested questioning his step mother "why can't i sit on my own father's lap?" A furious Suruchi berated him saying "only God can allow him that privilege. Go ask him"
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.