Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

224
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#communitygroup

0 posts0 participants0 posts today
W3C Developers<p>During the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> meeting in April 2025, <span class="h-card" translate="no"><a href="https://w3c.social/@plehegar" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>plehegar</span></a></span>, co-chair of the Process <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a> reported that the W3C Process document has been updated to align with bylaws and streamline workflows. <br>Changes include removing the <a href="https://w3c.social/tags/ProposedRecommendation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ProposedRecommendation</span></a> step, defining a new charter refinement process with simplified appeal rules, relaxing voting and consent thresholds, and allowing more groups to create registries. </p><p>🎬 Watch "Process Community Group Update": <a href="https://youtu.be/RX8CzWa1U0o" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/RX8CzWa1U0o</span><span class="invisible"></span></a></p>
W3C Developers<p>Last April, <span class="h-card" translate="no"><a href="https://schelling.pt/@domenic" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>domenic</span></a></span> reported that 7 AI LLM-based APIs are being developed in the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> web machine learning <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>. <br>▶️ <a href="https://webmachinelearning.github.io/incubations/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">webmachinelearning.github.io/i</span><span class="invisible">ncubations/</span></a></p><p>These APIs raise new <a href="https://w3c.social/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacy</span></a> and <a href="https://w3c.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> concerns and must keep pace with rapid <a href="https://w3c.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AI</span></a> advances. As part of the <a href="https://w3c.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Chrome</span></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 noreferrer" target="_blank">#<span>developers</span></a>.</p><p>🎬 Watch 'LLM-based APIs in browsers': <a href="https://youtu.be/N_4TUhsApHI" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/N_4TUhsApHI</span><span class="invisible"></span></a></p>
W3C Developers<p>As co-chair of the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> WebExtensions <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>, Simeon Vincent explains how web extensions—now embraced by major <a href="https://w3c.social/tags/browsers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>browsers</span></a>—enable a unified, web-based approach to browser extension development. </p><p>The group promotes cross-browser collaboration, responds to <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developers</span></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.</p><p>🎬 Watch "Web extensions at W3C": <a href="https://youtu.be/ltB9zqu82wI" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/ltB9zqu82wI</span><span class="invisible"></span></a></p>
W3C Developers<p>In this talk, <span class="h-card" translate="no"><a href="https://mas.to/@patrickbrosset" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>patrickbrosset</span></a></span>, of the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> WebDX <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>, covers two key efforts that both aim to make the <a href="https://w3c.social/tags/WebPlatform" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebPlatform</span></a> clearer and more accessible for <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developers</span></a>: <br>- web-features is a unified and shared catalog of features for consistent documentation and collaboration.<br>- Baseline simplifies this data by labeling features as “widely,” “newly,” or “limited” in availability, to help developers quickly assess feature support.</p><p>🎬 Watch "web-features and Baseline": <a href="https://youtu.be/QzfwNFIXOkM" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/QzfwNFIXOkM</span><span class="invisible"></span></a></p>
W3C Developers<p>[Security at W3C]</p><p>Last video from the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> SWAG <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a> meeting where Aaron Sim lists 3 meta questions: <br>- What’s the best UI to nudge <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developers</span></a> toward adopting security mitigations? <br>- How can we improve ecosystem-wide security for external code (e.g., node modules)? <br>- And how can we better promote <a href="https://w3c.social/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>security</span></a> practices among web developers?</p><p>🎬 <a href="https://youtu.be/CHsS48IcZ20" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/CHsS48IcZ20</span><span class="invisible"></span></a></p><p>The full playlist: <a href="https://www.youtube.com/playlist?list=PLNhYw8KaLq2Wr27HLfSTD4d6JpC3G0PVr" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/playlist?list=PLNh</span><span class="invisible">Yw8KaLq2Wr27HLfSTD4d6JpC3G0PVr</span></a></p>
W3C Developers<p>Plotting browser support data in a catalog shows the evolution of the web platform in terms of number and availability of features. </p><p>The <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> WebDX <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></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 noreferrer" target="_blank">#<span>developers</span></a>, along with support data across main <a href="https://w3c.social/tags/browsers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>browsers</span></a>. The catalog already powers <span class="h-card" translate="no"><a href="https://mastodon.social/@mdn" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mdn</span></a></span>, Can I use, and is now being integrated in tools and libraries.</p><p>▶️ <a href="https://www.w3.org/blog/2025/first-catalog-of-web-features-completed-by-the-webdx-community-group/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/blog/2025/first-catalog</span><span class="invisible">-of-web-features-completed-by-the-webdx-community-group/</span></a></p><p>Feedback welcome! <a href="https://github.com/web-platform-dx/web-features" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/web-platform-dx/web</span><span class="invisible">-features</span></a></p><p><span class="h-card" translate="no"><a href="https://w3c.social/@tidoust" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tidoust</span></a></span> <span class="h-card" translate="no"><a href="https://mas.to/@patrickbrosset" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>patrickbrosset</span></a></span></p>
W3C Developers<p>Based on the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> 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 noreferrer" target="_blank">#<span>CommunityGroup</span></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 noreferrer" target="_blank">#<span>security</span></a> mitigations against XSS.</p><p>▶️ <a href="https://www.w3.org/blog/2025/how-to-protect-your-web-applications-from-xss/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/blog/2025/how-to-protec</span><span class="invisible">t-your-web-applications-from-xss/</span></a> <br>cc <span class="h-card" translate="no"><a href="https://w3c.social/@simone" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>simone</span></a></span> <span class="h-card" translate="no"><a href="https://mastodon.social/@torgo" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>torgo</span></a></span></p><p>🎬 Security at W3C playlist: <a href="https://www.youtube.com/playlist?list=PLNhYw8KaLq2Wr27HLfSTD4d6JpC3G0PVr" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/playlist?list=PLNh</span><span class="invisible">Yw8KaLq2Wr27HLfSTD4d6JpC3G0PVr</span></a></p>
W3C Developers<p>📢 The <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> Credible Web <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></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 noreferrer" target="_blank">#<span>misinformation</span></a> on the web: <br>▶️ <a href="https://www.w3.org/events/workshops/2025/authentic-web-workshop/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/events/workshops/2025/a</span><span class="invisible">uthentic-web-workshop/</span></a></p><p>The first session on March 12 2025, will discuss a framework [<a href="https://kwz.me/hF8" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">kwz.me/hF8</span><span class="invisible"></span></a>] for assessing tools and advancing proposals to interoperable standards.</p><p>Attendance is free and open to all!!</p>
W3C Developers<p>🆕 <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> launches the Private Advertising Technology (PAT) <a href="https://w3c.social/tags/WorkingGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WorkingGroup</span></a><br>▶️ <a href="https://www.w3.org/groups/wg/pat/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/groups/wg/pat/</span><span class="invisible"></span></a></p><p>Motivated by the <span class="h-card" translate="no"><a href="https://w3c.social/@tag" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tag</span></a></span>'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 noreferrer" target="_blank">#<span>APIs</span></a> that support advertising without compromising user <a href="https://w3c.social/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>privacy</span></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 noreferrer" target="_blank">#<span>CommunityGroup</span></a>.</p><p>🎬 Watch <span class="h-card" translate="no"><a href="https://indieweb.social/@Chronotope" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>Chronotope</span></a></span> 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 noreferrer" target="_blank">#<span>w3cdevs2022</span></a>, Vancouver 🇨🇦: <a href="https://www.w3.org/2022/09/meetup/speaker-aram.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/2022/09/meetup/speaker-</span><span class="invisible">aram.html</span></a></p>
W3C Developers<p>🆕 <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> has launched the Sustainable Web <a href="https://w3c.social/tags/InterestGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InterestGroup</span></a> to create guidelines and best practices for addressing <a href="https://w3c.social/tags/sustainability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sustainability</span></a> challenges in digital technology affecting both people and the planet. </p><p>Drawing from the SustyWeb <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>’s work, the group will release the Web Sustainability Guidelines (WSG) 1.0, designed for end-users, tool developers, educators, and policymakers.<br>➡️ <a href="https://w3c.github.io/sustyweb/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">w3c.github.io/sustyweb/</span><span class="invisible"></span></a> </p><p>Read <span class="h-card" translate="no"><a href="https://w3c.social/@tzviya" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tzviya</span></a></span>'s post: <a href="https://www.w3.org/blog/2024/sustainable-web-interest-group-is-formed/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/blog/2024/sustainable-w</span><span class="invisible">eb-interest-group-is-formed/</span></a></p>
W3C Developers<p><a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3cTPAC</span></a><br>Several <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> groups have created videos showcasing work updates and demos. </p><p>Check out what's happening in the WebDX, WoT and <a href="https://w3c.social/tags/Solid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Solid</span></a> <a href="https://w3c.social/tags/CommunityGroups" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroups</span></a>, as well as in the <a href="https://w3c.social/tags/Accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Accessibility</span></a> Guidelines and <a href="https://w3c.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CSS</span></a> <a href="https://w3c.social/tags/WorkingGroups" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WorkingGroups</span></a>!</p><p>▶️ <a href="https://www.w3.org/2024/09/TPAC/group-updates.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/2024/09/TPAC/group-upda</span><span class="invisible">tes.html</span></a></p><p>CG <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a><br>WG <a href="https://w3c.social/tags/WorkingGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WorkingGroup</span></a></p>
W3C Developers<p>Taking over the Privacy <a href="https://w3c.social/tags/InterestGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InterestGroup</span></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 noreferrer" target="_blank">#<span>websites</span></a> do not sell or share personal information with third parties.<br>▶️ <a href="https://privacycg.github.io/gpc-spec/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">privacycg.github.io/gpc-spec/</span><span class="invisible"></span></a></p><p>GPC has been incubated in the Privacy <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>, and anchors its signal in several existing legal frameworks: <a href="https://privacycg.github.io/gpc-spec/#legal-effects" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">privacycg.github.io/gpc-spec/#</span><span class="invisible">legal-effects</span></a></p>
W3C Developers<p><a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3cTPAC</span></a> <br>Over the past 2 years of renewed activity within the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> <span class="h-card" translate="no"><a href="https://w3c.social/@wot" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>wot</span></a></span> <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>, numerous organizations, open-source projects, and researchers have demonstrated how they are incorporating <a href="https://w3c.social/tags/WoT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WoT</span></a> into their technology stacks across a variety of industries, incl. building and factory automation, energy, smart homes, and scientific instrumentation. </p><p>🎬 “Where is WoT?”: <a href="https://www.youtube.com/watch?v=sVZsLXaJqRw" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=sVZsLXaJqR</span><span class="invisible">w</span></a><br>cc <span class="h-card" translate="no"><a href="https://w3c.social/@ege" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>ege</span></a></span> <span class="h-card" translate="no"><a href="https://w3c.social/@crisdev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>crisdev</span></a></span></p>
W3C Developers<p><a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3cTPAC</span></a> <br>🎬 <a href="https://w3c.social/tags/developers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developers</span></a>, watch this presentation of the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> <a href="https://w3c.social/tags/WebDX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebDX</span></a> <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>: <a href="https://youtu.be/-LYBTdo189w" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/-LYBTdo189w</span><span class="invisible"></span></a></p><p><span class="h-card" translate="no"><a href="https://mas.to/@patrickbrosset" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>patrickbrosset</span></a></span> showcases efforts to catalog web platform features for integration into documentation sites and tools.This supports the <a href="https://w3c.social/tags/Baseline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Baseline</span></a> concept, helping developers understand current web capabilities. </p><p>Patrick also outlines the group's progress, its impact on <span class="h-card" translate="no"><a href="https://mozilla.social/@MDN" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>MDN</span></a></span>, Can I Use, and more, ending with a call to join and contribute!!<br><a href="https://github.com/web-platform-dx" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">github.com/web-platform-dx</span><span class="invisible"></span></a></p>
W3C Developers<p><a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3cTPAC</span></a> <br><span class="h-card" translate="no"><a href="https://w3c.social/@csarven" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>csarven</span></a></span>, of the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> <a href="https://w3c.social/tags/Solid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Solid</span></a> <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>, gives a demo of dokieli, a fully decentralized, browser-based authoring and annotation platform with built-in support for social interactions. </p><p>Dokieli makes use of various technical specifications such as Solid Protocol and Web Access Control that have been developed in the Solid Community Group.<br>▶️ <a href="https://dokie.li/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">dokie.li/</span><span class="invisible"></span></a></p><p>🎬 Watch the demo! <a href="https://youtu.be/_CpOxEkmYwk" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/_CpOxEkmYwk</span><span class="invisible"></span></a><br>cc <span class="h-card" translate="no"><a href="https://w3c.social/@yesvirginia" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>yesvirginia</span></a></span></p>
W3C Developers<p><a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3cTPAC</span></a> <br>The Per Resource Events Protocol (PREP) provides an alternative mechanism for notifications in <a href="https://w3c.social/tags/Solid" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Solid</span></a> </p><p>With PREP, apps get the current resource and notifications in one <a href="https://w3c.social/tags/HTTP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTP</span></a> request. Notifications can be content-negotiated, allowing different formats like metadata or representation deltas based on client preferences.</p><p> 🎬 In this video, Rahul Gupta, of the <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> Solid <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>, explains the fundamental concepts of PREP.<br>▶️ <a href="https://youtu.be/_IhysuBKz6Y" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">youtu.be/_IhysuBKz6Y</span><span class="invisible"></span></a><br>cc <span class="h-card" translate="no"><a href="https://w3c.social/@yesvirginia" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>yesvirginia</span></a></span></p>
W3C Developers<p>Newly created <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> <a href="https://w3c.social/tags/WorkingGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WorkingGroup</span></a>: "Linked Web Storage"! </p><p>The group's mission is to create <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebApps</span></a> with loosely coupled data storage, <a href="https://w3c.social/tags/authentication" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>authentication</span></a>, and access control by standardizing a <a href="https://w3c.social/tags/protocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>protocol</span></a> between apps and identity/storage servers.<br>▶️ <a href="https://www.w3.org/groups/wg/lws/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/groups/wg/lws/</span><span class="invisible"></span></a></p><p>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 noreferrer" target="_blank">#<span>Solid</span></a> Protocol developed by the Solid <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a></p>
W3C Developers<p>The <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> SVG <a href="https://w3c.social/tags/WorkingGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WorkingGroup</span></a> has been chartered until 30 June 2026 with the mission to maintain the <a href="https://w3c.social/tags/SVG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SVG</span></a> specification.<br>▶️ <a href="https://www.w3.org/2024/04/svg-wg.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/2024/04/svg-wg.html</span><span class="invisible"></span></a></p><p>The SVG group will also focus on testing the core SVG spec. to ensure quality and completeness, making necessary changes for better integration with <a href="https://w3c.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CSS</span></a> and <a href="https://w3c.social/tags/HTML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTML</span></a>. </p><p>No new features or proposals will be introduced; these will be handled by forums like the SVG <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a> or the Web Incubator <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a>.<br><a href="https://www.w3.org/community/groups/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/community/groups/</span><span class="invisible"></span></a></p>
W3C Developers<p>📢 <span class="h-card" translate="no"><a href="https://front-end.social/@openwebdocs" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>openwebdocs</span></a></span> published its "Impact and Transparency Report 2023":<br>▶️ <a href="https://openwebdocs.org/content/reports/2023/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">openwebdocs.org/content/report</span><span class="invisible">s/2023/</span></a></p><p>Notably, OWD both contributed and reviewed the greatest number of pull requests to the <span class="h-card" translate="no"><a href="https://mozilla.social/@MDN" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>MDN</span></a></span> content and browser compat data repos. It also completed the PWA doc rewrite and compat data updates. It joined <span class="h-card" translate="no"><a href="https://w3c.social/@w3c" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>w3c</span></a></span> WebDX <a href="https://w3c.social/tags/CommunityGroup" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CommunityGroup</span></a> (cc <span class="h-card" translate="no"><a href="https://mamot.fr/@tidoust" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tidoust</span></a></span> and <span class="h-card" translate="no"><a href="https://mas.to/@patrickbrosset" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>patrickbrosset</span></a></span>) to define baseline, and started Web security doc. research, etc., etc.</p><p><span class="h-card" translate="no"><a href="https://w3c.social/@dontcallmeDOM" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>dontcallmeDOM</span></a></span> (W3C) is a member of OWD's governing committee.</p>
ExploreLive feeds
About