← Feed

Posts

• Post #3031219

  RE: https://mastodon.social/@PavelASamsonov/116623276420116169 Browsers are open. Users can enter a new URL and jump to another site at any time. Apps are closed silos. Once a user downloads an app, the company will confine that user to its own territory. Also, web pages are limited by the browser's sandbox, making it difficult or impossible to access a user's contacts, device information, etc. Even if an app uses web technologies, it can still request more private data permiss...

• Post #3031218

  ReSpec is a tool for writing technical specifications as ordinary HTML. Wrote a guide about the basics needed to create and preview a ReSpec document: https://w3c.github.io/i18n-activity/guidelines/respec.html

• Post #2621922

  We've recently added automated testing to our i18n articles. From now on, before publishing, we'll automatically check common issues such as wrong language tags, date formats, and invalid markup.

• Post #2621921

  The new charter for the Internationalization Working Group has been adopted. We welcome everyone to join or rejoin the group: https://www.w3.org/International/groups/wg/charter-2026.html

• Post #2621920

  Happy 18th anniversary to the first draft of JLReq! 🎉

• Post #2621919

  @stuartyeates We would welcome the participation of relevant experts. In this area, in addition to knowledge of internationalization, a great deal of expertise regarding accessibility is also required.

• Post #2621918

  For those who attended W3C AC 2026, please feel free to write your feedback here: https://www.w3.org/wbs/34257/2026/

• Post #2621917

  Amazon employees are “tokenmaxxing” https://arstechnica.com/ai/2026/05/amazon-employees-are-tokenmaxxing-due-to-pressure-to-use-ai-tools/

• Post #932433

  The IETF HTTP WG mailing list has been hosted by the W3C since late 1997, because of practical considerations and the close collaboration between the IETF and W3C on HTTP standards. Prior to this, the HTTP WG’s mailing list was hosted by Hewlett-Packard Labs. This was the primary venue for discussions during the development of HTTP/1.0 (published as RFC 1945 in 1996) and early work on HTTP/1.1.

• Post #913230

  Use of Large Language Models in Standards Work is a Group Note on when LLMs can accelerate our work and when they create real risks. Must-read for anyone using AI in Web standards. https://www.w3.org/TR/llms-standards/

• Post #381588

  Many people have forgotten Tim Berners-Lee's article "Cool URIs don't change", which emphasizes that links should be designed to be persistent. It suggests avoiding elements that are prone to change in links to ensure their long-term validity. https://www.w3.org/Provider/Style/URI