Fuqiao Xue

@CinnamonCatYurilover@sharkey.skydevs.me The real nightmare is when Adobe Illustrator gets Artificial Intelligence ;-)

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

RE: @PavelASamsonov@mastodon.social

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 permissions during installation.

I hope PWAs will improve this situation.

Amazon employees are “tokenmaxxing”

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

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

@hdv@front-end.social it is about as meaningful as promoting engineers by lines of code written.

@leaverou@front-end.social The same applies to people. Don't deny your richness just because you're not understood for the time being.

@hdv@front-end.social We can give everyone a site, then let any app post to it via open standards :)

@stuartyeates@cloudisland.nz 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.

Back in 2008 W3C sat down with Japanese typesetting experts and created a clear, practical guide to how Japanese text really works so CSS, SVG, and HTML could support it properly on the web. Specs now point to JLReq for details, and it sparked similar language enablement guides for Arabic, Chinese, Korean, Tibetan, and many more. Real typographic knowledge, turned into web standards that make the global internet look right in every language.

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

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/

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

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.

@DiogoConstantino@masto.pt @killyourfm@layer8.space Any source?

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

@amirbkhan@mastodon.social Another possibility is that “this system isn't good for me either, but I believe that whatever I do won't change it. It's a complete waste of time. So it's better not to say anything.”

@jensimmons@front-end.social Service Workers

HTTP is fundamentally the protocol of the World Wide Web, making it a natural point of intersection between IETF (which focuses on core Internet protocols) and the W3C (which stewards Web technologies like HTML, CSS, and related specs). Today, the list remains active, with all HTTP WG drafts and RFCs directing comments there.

Although the HP list returned online on schedule in early January 1998, the HTTP WG did not migrate back. Instead, discussions continued on the W3C-hosted list. In the late 1990s, the IETF relied on volunteer-hosted or third-party servers for mailing lists. W3C, as a dedicated standards body with robust, publicly accessible email infrastructure optimized for technical discussions, provided a more stable alternative. The W3C’s lists.w3.org service has remained highly reliable.

In December 1997, the HP-hosted list went offline due to a combination of holiday (Christmas) site maintenance and the physical relocation of HP’s list server. The outage was expected to last from December 18, 1997, to January 5, 1998. To avoid disrupting ongoing discussions, W3C stepped in as a courtesy and quickly provisioned a temporary list at ietf-http-wg@w3.org.

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.

@sjmulder@bsd.network Search engines might use hreflang, but compared with the lang attribute, the results of hreflang are more difficult to verify. See also https://github.com/w3c/i18n-drafts/issues/405