The #Web turns 29 today and only half of the world’s population is online. To connect the other half, we #developers have to help close the digital divide and make the Web work for all! @timberners_lee@w3c#HappyBirthdayWWW
What is the TAG? Created by @w3c in 2001, the Technical Architecture Group serves #developers interests by driving consistent Web #design principles. Learn more: w3.org/2001/tag/@w3ctag
For this special election, the @w3c membership will fill 1 seat. Learn about the 3 great nominees and their respective statements: Andrew Betts @triblondon, Kenneth Rohde Christiansen @kennethrohde, and Theresa O'Connor @hoberw3.org/2018/03/05-tag-nomina… - Best of luck!
As highlighted last month, the new @w3c process document is granting an additional seat to @w3ctag (6 elected members instead of 5) w3.org/2018/Process-20180201…
... WOFF 2.0 is widely used on production #websites. It supports the entirety of the #TrueType and #OpenType specifications, including Variable fonts, Chromatic fonts, and font Collections. Read the doc. for more details: w3.org/TR/2018/REC-WOFF2-201…
... WOFF1.0 was released in Dec. 2012 and has been widely deployed since. To better lower the use of network bandwidth, while still allowing fast decompression (even on mobile devices!), the @w3c WebFonts #WorkingGroup worked on WOFF2.0
... Introduced in 2009, the Web Open Font Format (WOFF) was a milestone that marked the beginning of the #webfonts era. The idea was to specify a simple compressed file format for fonts, designed primarily for use on the #Web.
There are more to addressing #Spectre and #Meltdown than just reducing timers accuracy. The various browser vendors have started reporting on the work they see ahead of them
In particular, @mdrejhon has been expressing detailed concerns about the impact of reduced accuracy for some use cases (e.g. gaming). If you have ideas or concerns, head to the github repo github.com/w3c/hr-time/
The updated specification thus no longer suggests a minimum level of accuracy. There is still ongoing discussion on what the new recommendation should be github.com/w3c/hr-time/issue…
Indeed, the #Spectre and #Meltdown attacks revealed early January can be exploited in browsers - since these attacks rely on precise timing, reducing the precision of performance.now() was quickly identified as a way to reduce the risks of exploitation