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
Filter
Exclude
Time range
-
Near
All these considerations and more will be part of what workshop participants will discuss in September. If you want to contribute to the conversation, please submit an expression of interest or a position paper before August 17 - @w3c workshops are open to all, do not hesitate!
On the #Web, this is made all the more complicated as pages can be embedded in other pages, making the context of the permission request harder to understand for end #users.
1
And there is an art of how and when to ask for permission, in which Web app developers need to play their part - @mulligan shared his best practices on the matter a while ago: techcrunch.com/2014/04/04/th…
1
First, how informed is that consent? Very little if the request gets made when the page has hardly finished loading, or if the underlying risks are hard to grasp.
1
Browsers provide access to more and more features that cannot be granted to any random #Web site. One way to gate this access is by asking permission from the #user. But getting the user consent is not necessarily easy...
1
Next #W3CWorkshop will be looking at how to manage access to sensitive features in #Web #browsers! w3.org/Privacy/permissions-w… - hosted by @Qualcomm, September 18-19, in #SanDiego, CA 🇺🇸
This tweet is unavailable
1
1
2
In addition to the report, the slides, minutes and position papers of the workshop are all linked from the workshop page: w3.org/2017/11/web5g-worksho… Get in touch with @dontcallmeDOM if you want to be involved in the follow up task force
The report summarizes some of the main findings out of the presentations done at the workshop and paves the way to more detailed analysis as part of a follow-up Web5G task force.
1
The report of the Web5G workshop is out! w3.org/2017/11/web5g-worksho… This workshop was held back on May 10-11 hosted by @gsma in London 🇬🇧and has been looking at the intersections between the many innovations happening at the network layer and their impact on the app layer.
This tweet is unavailable
1
3
2
1
Yes, hurry up! The deadline is fast approaching (in 3 days). Please submit an application for a #diversity #scholarship so to participate in all @w3cTPAC meetings next October in #Lyon 🇫🇷 w3.org/2002/09/wbs/1/diversi…
Replying to @w3cdevs
#Web #developers and #designers who qualify should submit an application: w3.org/2002/09/wbs/1/diversi… Deadline to submit is 15 July. Hurry up!
1
1
日本語訳をありがとう!@omnidirect for XHTML+RDFa 1.1 - 第3版, XHTMLモジュール化によるRDFaのサポート asahi-net.or.jp/~ax2s-kmtn/i… #html5j #w3c_keio #html5j #w3c_keio @naomi5500
3
4
Project ideas are often about building a tool, playing with new gadgets, and brainstorming in the spirit of both contributing to the community and bringing technical challenges for individuals/teams.
1
1
It's #GeekWeek! Once a year, @w3c staff is taking a week to experiment, explore and innovate. It is a time to collaborate with colleagues with different expertise, or just learn about new trends and systems.
1
1
The proposed new charter includes new work on network error logging, an HTTP client hint for device memory and a generic reporting framework (usable for network error logs, CSP, etc) w3c.github.io/network-error-… w3c.github.io/device-memory/ w3c.github.io/reporting/ w3.org/2018/07/webperf-chart…
1
The Web Performance Working Group is the one bringing us all the key primitives for measuring #WebPerf: performance.now(), the various performance timelines (resources, user, paint, server) and more (beacon, page visibility, etc) w3.org/webperf/
This tweet is unavailable
1
2
More details on the meetup…
Have jusut updated the info for our next @w3ctag meet-the-tag (and friends) event ti.to/w3c-tag/meet-the-tag-s… in Seattle on July 26th, now featuring our first confirmed lightning speaker, @NellWaliczek on the #immersiveweb.
2
As #WebRTC gains more and more adoption, it needs to accommodate a growing number of usages, which the Working Group is expecting to address over time with these relatively small extensions (and probably bigger ones down the line…)
1
1
The #WebRTC DSCP Control API is an extension to the main #WebRTC spec to provide a more finegrained control on network QoS (quality of service) via DSCP (differentiated service code points) en.wikipedia.org/wiki/Differ… w3.org/TR/2018/WD-webrtc-dsc…
1
1