WebProNews

Tag: W3C

  • Google Restricting Cookies In Chrome To Improve Privacy

    Google Restricting Cookies In Chrome To Improve Privacy

    The days of cookies may be coming to an end as Google announces its plans to phase out third-party cookies within two years.

    The first indications of Google’s plans came in August when the company announced a new initiative called Privacy Sandbox. The initiative was founded in an effort to keep publishers from abusing technologies to track users. Specifically, many web publishers have found ways to work around blanket efforts to block third-party cookies with even more invasive types of tracking, such as fingerprinting. As Google describes:

    “With fingerprinting, developers have found ways to use tiny bits of information that vary between users, such as what device they have or what fonts they have installed to generate a unique identifier which can then be used to match a user across websites. Unlike cookies, users cannot clear their fingerprint, and therefore cannot control how their information is collected.”

    With today’s announcement, Google is looking for a more nuanced approach, one that addresses the needs of advertisers to make money in a way that does not abuse privacy. The company has been receiving feedback from W3C forums and other standards participants, feedback that indicates it is on the right track. Bolstered by this feedback, Google has committed to a timeline for its plans.

    “Once these approaches have addressed the needs of users, publishers, and advertisers, and we have developed the tools to mitigate workarounds, we plan to phase out support for third-party cookies in Chrome. Our intention is to do this within two years.”

    Google also plans to address other privacy issues, such as cross-site tracking and fingerprinting. The company has been under increasing scrutiny for Chrome’s privacy, or lack thereof. In June 2019, The Washington Post went so far as to label the browser “spy software,” and blamed it on Google’s position as both a browser maker and the single biggest cookie generator on the web. Relying on the search giant to protect user privacy is akin to relying on the fox to guard the henhouse.

    Hopefully Privacy Sandbox and Google’s commitment to phase out third-party cookies are a step in the right direction.

  • Web Creator Tim Berners-Lee Launches Contract for the Web and Says… Silos Shouldn’t Dominate Your Life

    Web Creator Tim Berners-Lee Launches Contract for the Web and Says… Silos Shouldn’t Dominate Your Life

    Tim Berners-Lee, the creator of the web, launches Contract for the Web that encourages companies to agree to let individuals own and control their data and importantly to allow mobility of data. Berners-Lee slammed social media saying that we have passed the “tipping point” and that “silos shouldn’t dominate your life.”

    The Contract for the Web asks companies to agree to certain principals that meet this overall objective:

    The web was designed to bring people together and make knowledge freely available. Everyone has a role to play to ensure the web serves humanity. By committing to the following principles, governments, companies, and citizens around the world can help protect the open web as a public good and a basic right for everyone.

    Tim Berners-Lee, the creator of the web and Director of the World Wide Web Consortium, recently discussed the Contract for the Web on CNBC:

    This Has Been a Tipping Point

    For a long time, like 20 years, I thought all I had to do is keep it (the web) free and open and people would do wonderful things. There was a Wikipedia and there are cats and there are wonderful things, but in fact, if you look at such people in the street now there’s been a big change. I think this has been a tipping point.

    The average person using the web is sometimes frustrated by the ads and sometimes they’re frustrated by not knowing what’s true. Sometimes they’re frustrated that they can’t really actually work with the people to build something new as they could. Sometimes they feel frustrated that they’re in different social networking silos that don’t talk to each other. In all kinds of ways you’re hearing both individuals, industry, press, and lots of commentators feel we could do better. The Contract for the Web is about everything. Let’s all get together and do better.

    Contract for the Web is About Working Together

    The Contract for the Web isn’t about (the concentration of power in big tech companies). The Contract for the Web is about needing all the big players and all of the little players working together. In a way, it’s healthy to have big players and little players because they each provide different things.

    What’s been interesting recently is the Data Transfer Project, where Google, Facebook, Twitter, and Microsoft all agreed that you can export your data from one and import it into another. To a certain extent, I think there’s been a push from individuals and to some extent from journalists to say that even though you might have these large silos, the silos shouldn’t dominate your life. You should be able to move from one to the other. You should be able to operate with data from wherever it comes from. It should be data that you can control.

  • W3C Appoints Two New Co-Chairs To Do Not Track Working Group

    W3C Appoints Two New Co-Chairs To Do Not Track Working Group

    The Do Not Track negotiations that have been taking place between advertisers and privacy advocates took a heavy blow yesterday when the Digital Advertising Alliance announced that it would be leaving the talks. Their departure caused some to wonder if the negotiations could continue without one of its major players, but the W3C has already put those fears to rest.

    The Hill reports that the W3C has named two new co-chairs to the Do Not Track working group. The first is Carl Cargill, Adobe’s Standards Principal, and the other is Justin Brookman, director of the Consumer Privacy Project at the Center for Democracy & Technology. The two will join existing chair Matthias Schunter, Chief Technologist at Intel.

    Now, the first question is whether or not these two new appointees are in any way related to the DAA walking out yesterday. The answer to that would be probably not as the W3C seems to have already selected these new co-chairs in response to former co-chair Peter Swire leaving the group to join President Obama’s NSA review panel.

    While the DAA’s departure may have not informed these decisions, the announcement was made official on Tuesday evening in response to their departure. On the official W3C blog, CEO Jeff Jaffe says that these new co-chairs will lead them forward with “renewed momentum.” He also hopes that the DAA will continue to watch the negotiations and rejoin once it sees that progress is being made.

    With its new co-chairs, the W3C had better hope that it’s able to make steady progress on reaching some kind of consensus in regards to Do Not Track standards. The DAA’s departure threatens the stability of the talks, and Washington is waiting with federal regulation in case the negotiations permanently break down.

    [Image: Center For Democracy & Technology]

  • DAA Pulls Out Of Do Not Track Negotiations

    The Do Not Track negotiations that have been taking place over the last year between advertisers and consumer advocates haven’t exactly gone over too well. The two sides have found very little common ground, and obstacles threatening to destabilize the talks arose more often than not. Now one of the major stakeholders is calling it quits.

    This afternoon, the Digital Advertising Alliance announced that it will be leaving the W3C Do Not Track working group after what it calls “two years of good-faith effort.” The organization says that it believes the working group is no longer “capable of fostering the development of a workable “do not track” solution.”

    The DAA’s departure comes almost two months after the organization’s most recent Do Not Track standards proposal was rejected by the working group at large. The DAA had hoped to limit some definitions and make any Do Not Track proposals more advertiser friendly, but the working group said that the DAA’s proposal didn’t jibe with its original charter.

    At that time, the DAA said that it “remain committed to any consensus process that seeks to keep control in the hands of Internet users.” That commitment seems to have dried up in the past two months as the group became increasingly frustrated with movements within the pro-privacy camp, including Mozilla’s decision to move ahead with its plan to block all third-party cookies before the Do Not Track working group had come to any consensus on the matter.

    So, what is the DAA going to do now that it’s pulled out of the negotiations? The organization said that it will keep doing what it’s been doing – moving ahead with its own standards:

    During more than two years since the W3C began its attempt at a dnt standard, the DAA has delivered real tools to millions of consumers. It has grown participation; enhanced transparency with more than a trillion ad impressions per month delivered with the DAA’s Icon making notice and choice information available within one-click of the ad; educated millions of consumers and provided browser-based persistent plug ins. The DAA has also succeeded in applying its principles to all of the participants in the digital ecosystem. Furthermore, we have expanded these consumer safeguards into 30 countries and clarified how the DAA’s Principles apply in the mobile Web and app environments.

    Going forward, the DAA intends to focus its time and efforts on growing this already-successful consumer choice program in “desktop,” mobile and in-app environments. The DAA is confident that such efforts will yield greater advances in consumer privacy and industry self-regulation than would its continued participation at the W3C.

    Now that the DAA has pulled out, where does that leave the current Do Not Track negotiations? The remaining members could try to salvage what’s left, but the DAA’s departure makes that unlikely. The negotiations are now in more danger of breaking down than ever before, and the threat of federal regulation is looming.

    Back in March, Sens. Jay Rockefeller and Richard Blumenthal introduced a bill called the The Do Not Track Online Act. The legislation, if enacted, would put the FTC in charge of doling out penalties to companies found violating Do Not Track standards. The Do Not Track working group was a chance for the various stakeholders to come together and create a set of voluntary standards they could all agree with.

    With the DAA’s departure and the imminent breakdown of negotiations, the advertising industry and privacy proponents may be left with federal regulations that serve neither side’s interests.

    [Image: Thinkstock]
    [h/t: The Hill]

  • Advertisers’ Proposal Gets Rejected In Latest Do Not Track Negotiations

    Earlier this year, the Do Not Track debate ran into a snag as the advertising groups and privacy proponents couldn’t even agree to disagree on a Do Not Track standard. This led to fears that the talks may just fall apart, but both groups were finally able to issue their own Do Not Track recommendations. Unsurprisingly, privacy proponents didn’t like what the advertisers suggested.

    CNET reports that the Digital Advertising Alliance proposed some changes to the Do Not Track proposal last month that would limit some definitions, including what tracking and retaining data means. The Tracking Protection Working Group, a coalition made up of advertisers, browser vendors and privacy proponents, issued an official response to the DAA’s proposal that outright rejects their suggestions.

    Was it fair of the Working Group to reject the advertiser’s proposal so quickly? Are advertisers getting fair representation in the Working Group? Let us know in the comments.

    The question to the group emphasized that the two texts varied importantly on four issues, with the decision today indicating the group’s subsequent direction on those issues, plus a topic that differs based on the logical implications of the four issues:

    1. Issue 5 – the definition of “tracking.” The DAA text is narrower in what is covered.

    2. Issue 16 — definitions of collecting, retaining, using, and sharing data. The DAA text is narrower in what is covered.

    3. Issue 188 – definition of de-identified data. The DAA text would treat data as “de-identified” in situations where the June text would not.

    4. Issue 199 – limitations on the use of unique identifiers. The June text would prohibit the use of unique identifiers where alternatives are reasonably available, thus limiting collection of user data in those circumstances.

    5. The effects of user choice. Under the June text, the Do Not Track mechanism would opt the user out of its broader definition of tracking. Under the DAA proposal, targeting of advertisements would not be affected by the Do Not Track standard; instead, users would use the separate DAA opt-out mechanism if they wished to limit targeted advertising.

    The Working Group were also unsatisfied with how the DAA’s proposal completely ignored what they feel are the two main pillars of Do Not Track – Do Not Target and Do Not Collect. For the former, they say that the DAA’s own tools don’t prevent users from being targeted, and therefore do no “meet the widely-understood meaning of Do Not Target.” As for the latter, the DAA stripped out a standard that called for advertisers to “not rely on unique identifiers for users or devices if alternative solutions are reasonably available.”

    Do you think the DAA was right in narrowing Do Not Track definitions? Or was the Working Group at large right to reject it? Let us know in the comments.

    In the end, the Working Group says it can’t move forward with the DAA’s proposal simply because it doesn’t fulfill the criteria that was laid out in the group’s charter:

  • 1. Consistent with the group’s charter. The charter says that a standard should define “mechanisms for expressing user preferences around Web tracking and for blocking or allowing Web tracking elements.” The DAA Proposal does not use the DNT signal to address either Do Not Target or Do Not Collect, and so does not fulfill the charter.
  • 2. Significant change from the status quo. The DAA Proposal data hygiene provisions address how to conduct market research and product development, but multiple comments state there is no significant change from the status quo. The overall comments indicate that the June Draft more clearly meets this criterion.
  • 3. Easy to explain why DNT:1 reduces tracking for participating sites. Based on discussions in the Group, and comments submitted, it is difficult to explain to users how the DAA Proposal reduces tracking for users who select DNT. Retargeting and profiling would continue unchanged. Collection would be unchanged, and the principal changes would be to how data is handled internally by companies after it is collected.
  • As you would expect, the advertising industry isn’t exactly happy with the Working Group rejecting its proposal:

    The broad industry proposal not selected by Professor Swire reflected the marketing and advertising community’s commitment to developing a working Do Not Track model that is true to our 2012 White House agreement and provides real choice to consumers, while at the same time protecting the economic engine of the Internet.

    Our organizations remain committed to any consensus process that seeks to keep control in the hands of Internet users.

    Unfortunately, the Do Not Track signal, as currently configured, does not and cannot reflect the real choices of Internet users. The signal has proven to be far too easy to hijack, allowing self-appointed intermediaries to turn DNT signals on, often without any knowledge, consent or input from users.

    The Working Group will continue to debate within the context of its original June proposal, but some players are already jumping the gun on implementing its own standards. Mozilla has been in the crosshairs of advertisers for most of this year as it moves ahead with a plan to block all third party cookies in Firefox. The non-profit recently shared a new plan that would allow it to target third party cookies without affecting the cookies that users are fine with, but advertisers say that Mozilla’s plan still negatively affects the ability of many small online businesses to serve targeted ads to consumers.

    All of this will likely come into play later this month as the Working Group meets to discuss changes to its current draft of standards. After that, it will work with browser vendors on how to best implement the agreed upon standards into Web browsers. Advertisers are likely to resist, but they might just end up agreeing with the Working Group at large in the end. It’s better to agree to voluntary standards than to invite government intervention – a fate that neither side wants.

    Do you think advertisers will go along with the Working Group at large to approve voluntary Do Not Track standards? Or will the government have to get involved? Let us know in the comments.

  • HTML5 Is Now Feature Complete, W3C To Start Focusing On Interoperability

    HTML5 Is Now Feature Complete, W3C To Start Focusing On Interoperability

    Many people will tell you that HTML5 is the future, while others will say that it’s not going to happen. The biggest proponent of and main architect behind HTML5, the World Wide Web Consortium, insist that HTML5 is the future, and its latest advancement only further helps to prove that point.

    The W3C recently published the “complete definition of HTML5 and Canvas 2D applications.” These are not W3C standards just yet, but it represents a major step forward for the Web technology. Those who were on the fence can now start developing for HTML5 in earnest as a stable version is now available.

    HTML5 may be stable and feature complete, but the W3C is not yet done with the Web standard. The group says that browser fragmentation still remains a problem with some browsers lagging behind others in terms of HTML5 adoption. The group’s new goal is to make sure HTML5 is interoperable across every browser. They hope to have this completed by the middle of 2014 and then it will publish its final HTML5 recommendation.

    A number of W3C members spoke out on this tremendous milestone. All express excitement that HTML5 is ready for its biggest debut yet. Here’s some of the more interesting testimonials with promises of a better future for all on the Web.

    Danny Winokur, Vice President and General Manager of Adobe Interactive Development, spoke on HTML5’s impact on the company’s recent introduction of its Edge Web tools:

    The completion of the HTML5 and Canvas specifications is an important milestone for developers and designers as it provides a common foundation for browsers and other implementations. Web standards are central to Adobe’s Edge Tools & Services for authoring rich interactive web media and animations, helping us deliver a more predictable and reliable user experience for anyone creating content and applications for the modern web. We congratulate the working group for their efforts in advancing both specifications.

    Tobie Langel, W3C Advisory Committee Representative for Facebook, spoke on the social network’s tight relationship with the Web technology:

    HTML5 plays a fundamental role in making Facebook accessible to the more than one billion people who use our products. Building with the latest web technologies is how we are able to make our experience available across more than 7,000 devices. Today’s announcement is an important milestone for the Open Web Platform. Facebook is proud to contribute to this effort through involvement in initiatives like the Coremob Community Group.

    Jean Paoli, President of Microsoft Open Technologies, spoke on Microsoft’s commitment to implementing HTML5 technologies in its products:

    Microsoft is proud to have participated in the hard work that has made HTML5 and Canvas 2D Candidate Recommendations, and congratulates W3C on reaching this important milestone. We look forward to working with the Web community to finalize these as W3C Recommendations. Several Microsoft products have implemented these emerging open Web standards to bring interoperability and maximum reach across multiple devices. We’re confident that HTML5 and Canvas 2D are ready for wide adoption, and glad that the industry shares our enthusiasm for HTML5.1 that will soon support better graphics and streaming media in an open way.

    It will be interesting to see how other players in the Web ecosystem approach HTML5 now that it’s “feature complete.” I know a few developers who have stuck to Flash and other plugin-based Web technologies because HTML5 just wasn’t good enough for them yet. It’s unknown if this will increase HTML5 adoption across the Web.

  • Do Not Track Negotiations In Danger Of Breaking Down

    Do Not Track Negotiations In Danger Of Breaking Down

    Do you remember Do Not Track? There was a big push earlier this year to standardize a method that would allow Internet users to opt out of ad tracking. Privacy advocates and lawmakers welcomed the move, but have yet to make any solid progress on the matter. A new report suggests that progress won’t be made anytime soon either.

    CNN Money reports that both sides in the Do Not Track debate have hit a wall in negotiations. Privacy advocates and online advertisers have been meeting for the past six months to discuss DNT and its implications. It would appear that the major blockade is that neither side is able to agree on what Do Not Track actually means.

    Where does that sound familiar? Oh right, Microsoft has been having the same issue since it announced that Internet Explorer 10 would have Do Not Track turned on by default. In response, the advertising industry told Microsoft that it was going to flat out ignore any DNT signals sent by IE10.

    To further complicate the issue, politicians have been exerting pressure on the advertising industry to accept the privacy advocates’ version of DNT. The Bi-Partisan Privacy Caucus called out the advertising industry back in early October, and accused it of putting “profits over privacy.” The caucus says the only solution is to pass legislation that defines what information advertisers can and can not collect online, especially when it comes to children.

    As for the advertising industry, the Direct Marketing Association has started an anti-DNT campaign called the Data-Driven Marketing Institute. The goal is to educate consumers on the benefits of targeted advertising. It argues that a majority of the online services consumers currently enjoy for free to little cost are supported by the same targeted ads that privacy advocates want to reign in.

    All of these different opinions on DNT have led to the stalemate we’re currently in. The whole DNT project faces an early death if these groups can not come to a compromise. That’s why the group overseeing the negotiations – the W3C – has hired Peter Swire, Ohio state law professor and former privacy official for both the Obama and Clinton administrations, to oversee the talks. His job is to push the parties into a compromise, and get a DNT plan up by the end of the year. That’s not likely to happen, and DNT is more and more likely to die the longer it stays like this.

    So what’s the plan from here on out? The W3C is now saying that it’s going to push all parties towards a consensus whether they like it or not. Ian Jacobs, spokesperson for the W3C, told CNN Money that the W3C “always seeks consensus, but when we can’t, we get votes and make decisions.” He said that one group simply saying “I don’t like this” isn’t going to be enough anymore.

    From the looks of it, the Do Not Track issue is going to be a thing well into the new year. The online advertising is unlikely to budge, and neither are privacy advocates. It will be interesting, however, to see if the W3C’s strategy of forceful intervention will work or not.

  • Google, Apple and Others Team Up To Promote Web Standards

    Google, Apple and Others Team Up To Promote Web Standards

    In some ways, the Web is like the lawless Wild West that you see in movies and television. There are no rules or standards for how things operate. Some organizations like W3C have tried to bring some form of order to the Web, but there’s not been a huge concentrated effort on the part of Web companies to standardize the Web. That all changes today.

    Google, Apple, Facebook and others have announced the immediate availability of Web Platform Docs. It’s only an alpha release for now, but its intentions are nothing short of grandiose. Google says that Web Platform Docs will be a “community-driven site that aims to become the comprehensive and authoritative source for web developer documentation.”

    The first release today is comprised of submissions from the Web Platform Stewards. These are the large companies that have contributed code, tutorials and more to help people create the future of the Web across all browsers. W3C started the site, but other parties like Facebook, HP and Nokia have submitted content for this first release.

    Web Platform Docs is hoping to put the future of Web development in the hands of those who are in the digital trenches day in and day out. These are the people who are constantly innovating the Web and Web Platform Docs gives them a voice to share their knowledge with those who may be just starting or are stuck on a particularly devious bit of code.

    The Web is a pretty wild place, and it will never be fully tamed. Web Platform Docs will hopefully cut down on a number of compatibility and formatting errors that still plague the Web. It may even get more people involved in Web development which can only be a good thing.

  • Facebook Updates Ringmark, Changes Coming To Coremob

    When someone says open source, the first company to pop in your mind is probably not Facebook. That would be a disservice to the company though as they are pushing open source just like the rest of them. The company started the Coremob W3C Community Group to push Web standards and they open sourced RIngmark, the company’s browser test suite for building apps on the mobile Web.

    The company open sourced Ringmark back at the beginning of April and they are already making loads of progress. They have changed the main page of Ringmark to now make it easier for developers to understand. When looking at the test results, it should be clear what use cases correlate with the tests.

    The bigger change coming to Ringmark is that it’s now integrated into Browserscope. This allows developers to see where each browser stands in regards to the three rings of Ringmark. The benefit here is that a new browser is added to the Web site’s stats every time a new browser hits up Ringmark.

    As for Facebook’s Coremob community, Robin Berjon, the co-chair of Coremob, will start to review the tests that Facebook has submitted. Once all the tests have been processed and added to Coremob’s Github, Ringmark will run off of these tests for its standards.

    Coremob will also continue to contribute to the development of Ringmark. Community suggestions like version numbers and moving certain standards to certain test rings have all come from community engagement. Continuing this kind of engagement will shape the future of the mobile Web, at least as far as Facebook is concerned.

    If you don’t really understand any of this, but still want to have an impact on the future of the mobile Web or just the Web in general, hit up rng.io in your browser. This will run the Ringmark test and send the results of your browser to Coremob. I ran the test on all three of my mobile browsers – Android, Firefox mobile and Opera Mini – and found that the default Android browser was the most advanced of the bunch in terms of adopting Web standards.

  • How HTML 5 Really Stacks Up To Incumbent Platforms [Infographic]

    HTML 5 is gaining strong industry backing from internet platform and mobile developers, but how does the revised language stack up against current king of the mountain Flash and other Web development platforms? With three years to go before the World Wide Web Consortium’s (W3C) goal of making HTML 5 the new industry standard, the language lags far behind currently preferred platforms in key metrics like reach, performance, API availability, and sound support. Here’s an infographic that breaks it down.

    Click the graphic to view a larger version.

    Of course, this graphic draws from current data about a language still in development. With industry backing as strong as it is, and as updated browsers and mobile devices are developed with stronger HTML 5 support, many of the language’s shortcomings will eventually become nonissues.

    [Via Get MOAI. Main Image Source: W3C]