MastodonTech.de

W3C DevelopersLast April, <a href="https://schelling.pt/@domenic" class="u-url mention" rel="nofollow noopener" target="_blank">@domenic</a> reported that 7 AI LLM-based APIs are being developed in the <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> web machine learning <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>. ▶️ <a href="https://webmachinelearning.github.io/incubations/" rel="nofollow noopener" translate="no" target="_blank">https://webmachinelearning.github.io/incubations/</a>These APIs raise new <a href="https://w3c.social/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> and <a href="https://w3c.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> concerns and must keep pace with rapid <a href="https://w3c.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> advances. As part of the <a href="https://w3c.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener" target="_blank">#Chrome</a> team, he suggests prioritizing high-level APIs, improving testing methods, and engaging ML experts in web standards to broaden AI accessibility for <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a>.🎬 Watch 'LLM-based APIs in browsers': <a href="https://youtu.be/N_4TUhsApHI" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/N_4TUhsApHI</a>

W3C DevelopersAs co-chair of the <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> WebExtensions <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>, Simeon Vincent explains how web extensions—now embraced by major <a href="https://w3c.social/tags/browsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#browsers</a>—enable a unified, web-based approach to browser extension development. The group promotes cross-browser collaboration, responds to <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a> needs, and works toward consistent implementation. Plans are underway to expand into both a feedback-driven community group and a specification-focused working group.🎬 Watch "Web extensions at W3C": <a href="https://youtu.be/ltB9zqu82wI" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/ltB9zqu82wI</a>

W3C DevelopersIn this talk, <a href="https://mas.to/@patrickbrosset" class="u-url mention" rel="nofollow noopener" target="_blank">@patrickbrosset</a>, of the <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> WebDX <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>, covers two key efforts that both aim to make the <a href="https://w3c.social/tags/WebPlatform" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebPlatform</a> clearer and more accessible for <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a>: - web-features is a unified and shared catalog of features for consistent documentation and collaboration. - Baseline simplifies this data by labeling features as “widely,” “newly,” or “limited” in availability, to help developers quickly assess feature support.🎬 Watch "web-features and Baseline": <a href="https://youtu.be/QzfwNFIXOkM" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/QzfwNFIXOkM</a>

Dan QThe WebDX <a href="https://m.danq.me/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a> at <a href="https://w3c.social/@w3cdevs" class="u-url mention" rel="nofollow noopener" target="_blank">@w3cdevs</a> have reached a milestone in their efforts to catalogue <a href="https://m.danq.me/tags/Web" class="mention hashtag" rel="nofollow noopener" target="_blank">#Web</a> browser baseline features, and that's great! ❤️But I worry that some <a href="https://m.danq.me/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a> will look at graphs like this one and think "more features == better". And I'm not sure whether or not that's actually true. From some <a href="https://m.danq.me/tags/DX" class="mention hashtag" rel="nofollow noopener" target="_blank">#DX</a> perspectives (and many <a href="https://m.danq.me/tags/UX" class="mention hashtag" rel="nofollow noopener" target="_blank">#UX</a> perspectives), widespread implementation of a new feature can be a net harm, not good.🔗 Deeper dive (choose your preferred medium!): - <a href="https://danq.me/webdx-does-more-mean-better" rel="nofollow noopener" translate="no" target="_blank">https://danq.me/webdx-does-more-mean-better</a> - <a href="gemini://danq.me/posts/webdx-does-more-mean-better" rel="nofollow noopener" translate="no" target="_blank">gemini://danq.me/posts/webdx-does-more-mean-better</a> - <a href="https://textplain.blog/does-more-mean-better" rel="nofollow noopener" translate="no" target="_blank">https://textplain.blog/does-more-mean-better</a><a href="https://m.danq.me/tags/WebBrowser" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebBrowser</a> <a href="https://m.danq.me/tags/WebBrowsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebBrowsers</a> <a href="https://m.danq.me/tags/browsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#browsers</a> <a href="https://m.danq.me/tags/standards" class="mention hashtag" rel="nofollow noopener" target="_blank">#standards</a>

W3C Developers[Security at W3C]Last video from the <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> SWAG <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a> where Aaron Sim lists 3 meta questions: - What’s the best UI to nudge <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a> toward adopting security mitigations? - How can we improve ecosystem-wide security for external code (e.g., node modules)? - And how can we better promote <a href="https://w3c.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> practices among web developers?🎬 <a href="https://youtu.be/CHsS48IcZ20" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/CHsS48IcZ20</a>The full playlist: <a href="https://www.youtube.com/playlist?list=PLNhYw8KaLq2Wr27HLfSTD4d6JpC3G0PVr" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/playlist?list=PLNhYw8KaLq2Wr27HLfSTD4d6JpC3G0PVr</a>

W3C DevelopersPlotting browser support data in a catalog shows the evolution of the web platform in terms of number and availability of features. The <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> WebDX <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a> has completed a first nearly complete catalog of web features targeted at web <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener" target="_blank">#developers</a>, along with support data across main <a href="https://w3c.social/tags/browsers" class="mention hashtag" rel="nofollow noopener" target="_blank">#browsers</a>. The catalog already powers <a href="https://mastodon.social/@mdn" class="u-url mention" rel="nofollow noopener" target="_blank">@mdn</a>, Can I use, and is now being integrated in tools and libraries.▶️ <a href="https://www.w3.org/blog/2025/first-catalog-of-web-features-completed-by-the-webdx-community-group/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/blog/2025/first-catalog-of-web-features-completed-by-the-webdx-community-group/</a>Feedback welcome! <a href="https://github.com/web-platform-dx/web-features" rel="nofollow noopener" translate="no" target="_blank">https://github.com/web-platform-dx/web-features</a><a href="https://w3c.social/@tidoust" class="u-url mention" rel="nofollow noopener" target="_blank">@tidoust</a> <a href="https://mas.to/@patrickbrosset" class="u-url mention" rel="nofollow noopener" target="_blank">@patrickbrosset</a>

W3C DevelopersBased on the <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> workshop "Secure the Web Forward” and thanks to work taking place in the W3C Security Web Application Guidelines (SWAG) <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>, we are happy to release 6 videos that address the complexities of Content Security Policy and Trusted Types, by introducing open-source tooling that reduce uncertainty and complexity of configuring web <a href="https://w3c.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> mitigations against XSS.▶️ <a href="https://www.w3.org/blog/2025/how-to-protect-your-web-applications-from-xss/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/blog/2025/how-to-protect-your-web-applications-from-xss/</a> cc <a href="https://w3c.social/@simone" class="u-url mention" rel="nofollow noopener" target="_blank">@simone</a> <a href="https://mastodon.social/@torgo" class="u-url mention" rel="nofollow noopener" target="_blank">@torgo</a>🎬 Security at W3C playlist: <a href="https://www.youtube.com/playlist?list=PLNhYw8KaLq2Wr27HLfSTD4d6JpC3G0PVr" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/playlist?list=PLNhYw8KaLq2Wr27HLfSTD4d6JpC3G0PVr</a>

W3C Developers📢 The <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> Credible Web <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a> is hosting a mini-workshop series to review proposals aimed at combating <a href="https://w3c.social/tags/misinformation" class="mention hashtag" rel="nofollow noopener" target="_blank">#misinformation</a> on the web: ▶️ <a href="https://www.w3.org/events/workshops/2025/authentic-web-workshop/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/events/workshops/2025/authentic-web-workshop/</a>The first session on March 12 2025, will discuss a framework [<a href="https://kwz.me/hF8" rel="nofollow noopener" translate="no" target="_blank">https://kwz.me/hF8</a>] for assessing tools and advancing proposals to interoperable standards.Attendance is free and open to all!!

W3C Developers🆕 <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> launches the Private Advertising Technology (PAT) <a href="https://w3c.social/tags/WorkingGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#WorkingGroup</a> ▶️ <a href="https://www.w3.org/groups/wg/pat/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/groups/wg/pat/</a>Motivated by the <a href="https://w3c.social/@tag" class="u-url mention" rel="nofollow noopener" target="_blank">@tag</a>'s Ethical Web Principles, this group aims to define web features and <a href="https://w3c.social/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a> that support advertising without compromising user <a href="https://w3c.social/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a>. The group will produce specifications for user agents, building on work incubated in the <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>.🎬 Watch <a href="https://indieweb.social/@Chronotope" class="u-url mention" rel="nofollow noopener" target="_blank">@Chronotope</a> giving an excellent overview of the PAT work, back in 2022 at <a href="https://w3c.social/tags/w3cdevs2022" class="mention hashtag" rel="nofollow noopener" target="_blank">#w3cdevs2022</a>, Vancouver 🇨🇦: <a href="https://www.w3.org/2022/09/meetup/speaker-aram.html" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/2022/09/meetup/speaker-aram.html</a>

W3C Developers🆕 <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> has launched the Sustainable Web <a href="https://w3c.social/tags/InterestGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#InterestGroup</a> to create guidelines and best practices for addressing <a href="https://w3c.social/tags/sustainability" class="mention hashtag" rel="nofollow noopener" target="_blank">#sustainability</a> challenges in digital technology affecting both people and the planet. Drawing from the SustyWeb <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>’s work, the group will release the Web Sustainability Guidelines (WSG) 1.0, designed for end-users, tool developers, educators, and policymakers. ➡️ <a href="https://w3c.github.io/sustyweb/" rel="nofollow noopener" translate="no" target="_blank">https://w3c.github.io/sustyweb/</a> Read <a href="https://w3c.social/@tzviya" class="u-url mention" rel="nofollow noopener" target="_blank">@tzviya</a>'s post: <a href="https://www.w3.org/blog/2024/sustainable-web-interest-group-is-formed/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/blog/2024/sustainable-web-interest-group-is-formed/</a>

W3C Developers<a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#w3cTPAC</a> Several <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> groups have created videos showcasing work updates and demos. Check out what's happening in the WebDX, WoT and <a href="https://w3c.social/tags/Solid" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solid</a> <a href="https://w3c.social/tags/CommunityGroups" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroups</a>, as well as in the <a href="https://w3c.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener" target="_blank">#Accessibility</a> Guidelines and <a href="https://w3c.social/tags/CSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSS</a> <a href="https://w3c.social/tags/WorkingGroups" class="mention hashtag" rel="nofollow noopener" target="_blank">#WorkingGroups</a>!▶️ <a href="https://www.w3.org/2024/09/TPAC/group-updates.html" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/2024/09/TPAC/group-updates.html</a>CG <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a> WG <a href="https://w3c.social/tags/WorkingGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#WorkingGroup</a>

W3C DevelopersTaking over the Privacy <a href="https://w3c.social/tags/InterestGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#InterestGroup</a>'s role in reviewing and advising other groups on enhancing user privacy in Web standards, the group will also develop the Global Privacy Control (GPC) spec., which defines a signal sent via HTTP and the DOM to request that <a href="https://w3c.social/tags/websites" class="mention hashtag" rel="nofollow noopener" target="_blank">#websites</a> do not sell or share personal information with third parties. ▶️ <a href="https://privacycg.github.io/gpc-spec/" rel="nofollow noopener" translate="no" target="_blank">https://privacycg.github.io/gpc-spec/</a>GPC has been incubated in the Privacy <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>, and anchors its signal in several existing legal frameworks: <a href="https://privacycg.github.io/gpc-spec/#legal-effects" rel="nofollow noopener" translate="no" target="_blank">https://privacycg.github.io/gpc-spec/#legal-effects</a>

W3C DevelopersNewly created <a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener" target="_blank">@w3c</a> <a href="https://w3c.social/tags/WorkingGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#WorkingGroup</a>: "Linked Web Storage"! The group's mission is to create <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebApps</a> with loosely coupled data storage, <a href="https://w3c.social/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a>, and access control by standardizing a <a href="https://w3c.social/tags/protocol" class="mention hashtag" rel="nofollow noopener" target="_blank">#protocol</a> between apps and identity/storage servers. ▶️ <a href="https://www.w3.org/groups/wg/lws/" rel="nofollow noopener" translate="no" target="_blank">https://www.w3.org/groups/wg/lws/</a>The group will deliver the Linked Web Storage Protocol specification, based among other input on the the <a href="https://w3c.social/tags/Solid" class="mention hashtag" rel="nofollow noopener" target="_blank">#Solid</a> Protocol developed by the Solid <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#CommunityGroup</a>

westbrookThe <a href="https://mastodon.social/tags/webComponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webComponents</a> <a href="https://mastodon.social/tags/communityGroup" class="mention hashtag" rel="nofollow noopener" target="_blank">#communityGroup</a> at the <a href="https://mastodon.social/tags/w3c" class="mention hashtag" rel="nofollow noopener" target="_blank">#w3c</a> is beginning to put together background info for their yearly report on <a href="https://mastodon.social/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a> <a href="https://mastodon.social/tags/specs" class="mention hashtag" rel="nofollow noopener" target="_blank">#specs</a> and <a href="https://mastodon.social/tags/proposals" class="mention hashtag" rel="nofollow noopener" target="_blank">#proposals</a> in support of better, faster, broader development of web components. If you've got thoughts, come share them at <a href="https://github.com/w3c/webcomponents-cg/discussions/66" rel="nofollow noopener" target="_blank">https://github.com/w3c/webcomponents-cg/discussions/66</a>The more voices the better, so if you've got pain points or wins or big ideas to share with other devs of the broader W3C community, come on down!---Read up on past reports, here: <a href="https://w3c.github.io/webcomponents-cg/" rel="nofollow noopener" target="_blank">https://w3c.github.io/webcomponents-cg/</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#communitygroup