Get involved in @w3c and give input on all of our specs. See also youtube.com/@W3COfficial and @w3cdevs@w3c.social. By @dontcallmeDOM and @marieforgue
Joined October 2014
- Tweets 4,375
- Following 608
- Followers 11,339
- Likes 2,472
3-5 Dec.: The @w3ctag meets in #Cupertino 🇺🇸 to discuss about current core design components of the #Web github.com/w3ctag/meetings/t…
1
1
Happy Cyber Monday! Don’t miss out — save 20% on your purchase of programs and verified certificates! Applies to @thew3c #FrontEnd Web #Developer #CSS #HTML5 #JavaScript @edXOnline
8
7
Hear directly from @fantasai and @plhw3org on the motivations and directions for this process evolution in a presentation they gave at our #w3cTPAC meetings last September: w3.org/2019/09/TPAC/tp-conti… (video+transcript+slides).
2
1
1
... the @W3CAB has been building a full proposal on how to adopt the W3C Recommendation track to allow this kind of iteration for our standards: w3.org/wiki/Process2020
1
1
1
A major focus on the next revision of the process is to enable more continuous evolution of #W3CStandards. Because the stage-based approach to standardization is sometimes a hindrance to groups that need fast iteration for their work, ...
1
1
The W3C Process is maintained by the @W3CAB, with most of the work happening in public in the W3C Process Community Group
The process is maintained by our Advisory Board @w3CAB (yes, they too are on Twitter!) with input from the public via the W3C Process Community Group w3.org/community/w3process/
Congrats to @chaals for shepherding that latest set of updates!
1
1
Back in 2018, concerns were raised with regard to how the precision in the clock could help mount #Spectre and #Meltdown attacks - the clock resolution was lowered to 5 microseconds to reduce the risks w3.org/TR/hr-time-2/#clock-r…
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
This specification defines performance.now(), a precise and monotonic clock for Web #apps. It provides the current time in sub-millisecond resolution #security #performance. Check the good browser support: caniuse.com/#feat=high-resol…
1
Congrats to editor @igrigorik for the released @w3c #WebStandard "High Resolution Time Level 2" #timetoadopt
This tweet is unavailable
1
See current browser support caniuse.com/#feat=servicewor… and the #github repo: github.com/w3c/ServiceWorker…
1
In addition to the offline capabilities, #ServiceWorkers handle notifications, perform heavy calculations on a separate thread, and more. It is a powerful tool for Web #developers!
1
#timetoadopt this important specification that notably make #PWAs work offline! w3.org/TR/2019/CR-service-wo…
This tweet is unavailable
1
5
6
W3C Developers (@w3cdevs@w3c.social) retweeted
What can you do with a Decentralized Identifier that you can't do now? First public working draft of the @w3c DID WG Use Cases doc now published at w3.org/TR/did-use-cases/. Let us know if you have more UCs please. (Nice to be an editor on behalf of @gs1).
1
1
12
For additional info, watch the videos of the talks: vimeo.com/showcase/6176604
Read also the workshop report itself that reflects the discussions on threading support, WebIDL Bindings in #WebAssembly, latency, cloud gaming, #monetization, indie #games, and more:
w3.org/2018/12/games-worksho…
1
1
Lots of progress on the standardization front for the ideas raised during the #w3cgames2019 #W3CWorkshop six months ago! Read @tidoust's post: w3.org/blog/2019/11/status-u…
1