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
@w3ctag member @lukOlejnik wants to make the Web a safer place! Read his #bio lukaszolejnik.com/about or blog at blog.lukaszolejnik.com #security #privacy
1
"It's taken many years of work by [@Tsyesika ], Chris Webber and many people in the @SocialWebWG . I'm thankful to all of those who helped bring this forward. I hope this standard will help shape social applications allowing them to be more open" nitter.vloup.ch/i/web/status/956…
Not to be missed! @w3ctag #meetup in London to 1) meet & greet newly elected
@lukOlejnik 2) learn what the TAG is up to and 3) give feedback about TAG's current priorities: ti.to/w3c-tag/meet-the-tag-l…
1
7
1
7
The focus of the most recent discussion though is on the evolution of the real-time connection API lists.w3.org/Archives/Public…
1
The group has also a few additional APIs to enable screen sharing, recording, quality monitoring - these too will need attention for greater adoption and interoperability. w3.org/2011/04/webrtc/
1
Given the peer-to-peer nature of the tech, there is even a separate dedicated system to identify specific bugs when a given browser tries to connect with another specific one github.com/webrtc/KITE
1
A lot of the group's efforts will be to push for convergence of browser implementations via increased attention to its test suite github.com/w3c/web-platform-…
1
These 2 APIs are already adopted across all modern browsers, although there are still quite a few incompatibilities among them. caniuse.com/#search=webrtc
1
Two main components of that series enable access to mic and cameras w3.org/TR/mediacapture-strea… and then provide the building blocks to establish a real-time connection between a browser and another peer (possibly another browser) w3.org/TR/webrtc/
1
Another Working Group is looking at its work plan for the upcoming year: the WebRTC Working Group. That group is responsible for a series of specification that enables p2p real-time audio/video/data exchange on the Web.
The @w3payments Working Group released yesterday its roadmap of work for 2018 lists.w3.org/Archives/Public… . This is the group developing new features to facilitate and improve payments in Web browsers.
1
1
@w3payments is undoubtly well-positioned to significantly change how we use on-line payments and what for. Watch this space, experiment with the APIs and contribute your feedback!
1
Finally, the group will be on the look for new method of payments: the current work enables credit cards, native apps and Web apps to act as payment system. A lot of innovation is happening in that sphere (cryptocurrencies, interledger) that may have specific integration needs.
1
2
4
Likewise, this can facilitate the adoption of stronger authentication mechanisms, such as 3D secure or the 2-factor authentication mechanisms being developed by another W3C Working Group, Web Authentication w3.org/webauthn
1
2
1
2
The group also wants to increase built-in security for on-line payments: once the browser manages payment data, merchants can opt not to receive sensitive data (e.g. card numbers) directly, and instead get a proof of a payment order from the user - known as tokenization.
1
1
The idea is that if you want to develop a new e.g. paypal, it will make it easier for merchants to include your service among their payment options, and make the over payment flow a lot more user-friendly.
1
1
Beyond this, the 2018 roadmap includes pushing further experimentation with another major work item of the group: Payment Handler w3.org/TR/payment-handler/. That API enables innovation in online payments by facilitating integration of Web sites as payment providers.
1
1
1
If you're interested in adopting it in your projects, developer.mozilla.org/en-US/… and github.com/w3c/payment-reque… are good starting points - and as always, your feedback on the API is most welcomed at github.com/w3c/payment-reque…
1
1
Combined with the no-install / just-in-time quality of the Web, it creates brand new opportunities. You could imagine e.g. to get tourists to pay for a bus ticket by flashing a QR code. Or even better, YOU could imagine new usages 😋
1
1
Part of the 2018 roadmap is to get further adoption from merchants as highlighted by the group's staff contact @ibjacobs w3.org/blog/wpwg/2017/12/14/…
1
1