veganism.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Veganism Social is a welcoming space on the internet for vegans to connect and engage with the broader decentralized social media community.

Administered by:

Server stats:

299
active users

#w3c

6 posts6 participants0 posts today
mage_of_dragons<p>For HTML6, I'd like to see a ``&lt;nobody&gt;``-tag, that displays when you want your website to feel lonely.</p><p><a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://mastodon.social/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>html</span></a> <a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webdev</span></a> <a href="https://mastodon.social/tags/webdevelopment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webdevelopment</span></a> <a href="https://mastodon.social/tags/w3c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3c</span></a> <a href="https://mastodon.social/tags/www" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>www</span></a></p>
Thor A. Hopland<p>(7/7) In short, we say <a href="https://snabelen.no/tags/WebSocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebSocial</span></a> instead of the <a href="https://snabelen.no/tags/Fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Fediverse</span></a> to truly unlock the potential of what it can be, and that is a communication system built on top of established, decentralized technology, under the umbrella of none other than <a href="https://snabelen.no/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a>.</p><p>By unpoliticizing the word, we've basically given it verbage and actual purpose. Are you going to post content on <a href="https://snabelen.no/tags/WebSocial" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebSocial</span></a> with <a href="https://snabelen.no/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ActivityPub</span></a>? How will you do it? Single user? Multi user? Actual platform?</p><p>Giving creators that power can foster magic.</p>
Antonin Delpeuch<p><span class="h-card" translate="no"><a href="https://post.lurk.org/@lozross" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>lozross</span></a></span> <span class="h-card" translate="no"><a href="https://openbiblio.social/@tibosl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tibosl</span></a></span> <span class="h-card" translate="no"><a href="https://openbiblio.social/@tibhannover" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>tibhannover</span></a></span> very nice! it looks like the <a href="https://mamot.fr/tags/TS4NFDI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TS4NFDI</span></a> project is closely aligned with the aims of the <a href="https://mamot.fr/tags/reconciliation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>reconciliation</span></a> <a href="https://mamot.fr/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> community group (<a href="https://www.w3.org/community/reconciliation/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/community/reconciliatio</span><span class="invisible">n/</span></a>) and its protocol (<a href="https://www.w3.org/community/reports/reconciliation/CG-FINAL-specs-0.2-20230410/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">w3.org/community/reports/recon</span><span class="invisible">ciliation/CG-FINAL-specs-0.2-20230410/</span></a>) - do you know if there is awareness of this protocol and any plans to do something with it?</p>
Inautilo<p><a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Development</span></a> <a href="https://mastodon.social/tags/Proposals" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Proposals</span></a><br>How do we evolve CSS logical shorthands? · There are options, but one major roadblock <a href="https://ilo.im/1630tm" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/1630tm</span><span class="invisible"></span></a></p><p>_____<br><a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CSS</span></a> <a href="https://mastodon.social/tags/Shorthand" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Shorthand</span></a> <a href="https://mastodon.social/tags/LogicalProperties" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>LogicalProperties</span></a> <a href="https://mastodon.social/tags/Specification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Specification</span></a> <a href="https://mastodon.social/tags/CSSWG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CSSWG</span></a> <a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Frontend</span></a></p>
Inautilo<p><a href="https://mastodon.social/tags/Development" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Development</span></a> <a href="https://mastodon.social/tags/Announcements" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Announcements</span></a><br>CSS Mixins are ready to explore · How you can enable the feature in Chrome Canary <a href="https://ilo.im/162zz3" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">ilo.im/162zz3</span><span class="invisible"></span></a></p><p>_____<br><a href="https://mastodon.social/tags/ModernCSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ModernCSS</span></a> <a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> <a href="https://mastodon.social/tags/Specification" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Specification</span></a> <a href="https://mastodon.social/tags/CssMixins" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CssMixins</span></a> <a href="https://mastodon.social/tags/CssFunctions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CssFunctions</span></a> <a href="https://mastodon.social/tags/Chrome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Chrome</span></a> <a href="https://mastodon.social/tags/Browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Browser</span></a> <a href="https://mastodon.social/tags/WebDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebDev</span></a> <a href="https://mastodon.social/tags/Frontend" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Frontend</span></a> <a href="https://mastodon.social/tags/CSS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CSS</span></a></p>
Ramesh #NotGoingBack<p>⬆️ <span class="h-card" translate="no"><a href="https://flx.masto.host/@bosak" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>bosak</span></a></span> <span class="h-card" translate="no"><a href="https://carhenge.club/@skiles" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>skiles</span></a></span></p><p>&gt;&gt; Twenty-five years ago I was part of an effort… to develop a standard environment for the exchange of business documents called <a href="https://mastodon.social/tags/ebXML" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ebXML</span></a>. It was an open-standards internet follow-on to <a href="https://mastodon.social/tags/EDI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EDI</span></a>. … an environment in which all the actual business transactions were between machines, without the need for human…</p><p>Then, <span class="h-card" translate="no"><a href="https://w3c.social/@timbl" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>timbl</span></a></span> and <a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> invented the <a href="https://mastodon.social/tags/SemanticWeb" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SemanticWeb</span></a> and <a href="https://mastodon.social/tags/OWL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OWL</span></a> reasoners, which I can't help but see as a precursor to the current AI push, and a continuation of that way of thinking</p>
@reiver ⊼ (Charles) :batman:<p>W3C Web Annotations Workshop<br><a href="https://youtube.com/playlist?list=PLmuJEyeapl2dkAVxc8pJhxbWFfChS5OHT" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">youtube.com/playlist?list=PLmu</span><span class="invisible">JEyeapl2dkAVxc8pJhxbWFfChS5OHT</span></a></p><p><a href="https://mastodon.social/tags/WebAnnotations" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebAnnotations</span></a> <a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a></p>
100% TAX :verified: :verified:<p>The Tor Project is actually verified from torproject.org...including Mullvad being verified too...<br>EFF is too!(verfied too!)</p><p>torproject@mastodon.social<br>mullvadnet@mastodon.online<br>eff@mastodon.social</p><p>🎈 <br>🌋 🥳 mastodon.archive.org 🎉 ⚠️ </p><p>Then archive.org even cooler ❕❗❕<br>☢️ They are on the fediverse with their own instance!!! So is w3c!<br>☢️</p><p>w3c@w3c.social</p><p><a href="https://mastodon.social/tags/fediverse" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>fediverse</span></a> <a href="https://mastodon.social/tags/Mastodon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mastodon</span></a> <a href="https://mastodon.social/tags/Tor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Tor</span></a> <a href="https://mastodon.social/tags/TorProject" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TorProject</span></a> <a href="https://mastodon.social/tags/EFF" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EFF</span></a> <a href="https://mastodon.social/tags/Mullvad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mullvad</span></a> <a href="https://mastodon.social/tags/w3c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3c</span></a> <a href="https://mastodon.social/tags/MullvadVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MullvadVPN</span></a> <a href="https://mastodon.social/tags/ElectronicFrontierFoundation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ElectronicFrontierFoundation</span></a></p>
João S. O. Bueno<p>Forr those of you who still believe in something as an "open web" : Cloudfare, for one, is in a position to determine what you can use and can't to browse the web - and they are blocking everything non-bigtech. (Mozilla included in "bigtech" for this purpose): </p><p><a href="https://forum.palemoon.org/viewtopic.php?p=260689#p260689" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">forum.palemoon.org/viewtopic.p</span><span class="invisible">hp?p=260689#p260689</span></a></p><p><a href="https://floss.social/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>web</span></a> <a href="https://floss.social/tags/w3c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3c</span></a> <a href="https://floss.social/tags/OpenStandards" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenStandards</span></a></p>
Maho Pacheco 🦝🍻<p>When you are looking at implementing the current W3C recommendation to sign documents, and you need to travel to the future, 6 days.</p><p> <a href="https://hachyderm.io/tags/technology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>technology</span></a> <a href="https://hachyderm.io/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> <a href="https://hachyderm.io/tags/documents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>documents</span></a> <a href="https://hachyderm.io/tags/future" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>future</span></a></p>
Tantek Çelik<p>Something I wrote in the W3C Authentic Web Mini Workshop’s Zoom chat:<br><br><br>Another implicit assumption (flaw) that is often a part of "purely technical solutions" is the neglect or ignorance (innocent naïveté) of existing technical solutions.<br> <br>A technical proposal should not be praised for what it claims to solve.<br> <br>A technical proposal must be evaluated by what marginal difference or advantage does it provide over existing technologies.<br> <br>Any technical proposal that ignores prior technologies is itself doomed to be ignored by the next technical proposal.<br><br><br>In addition to the slide presentations (links to come) in the mini workshop and Zoom verbal discussion which was minuted (link to come), there was a lot of very interesting discussion in the Zoom chat, which was not minuted. Sometimes such quick back &amp; forth can help inspire summarizing of points which one had not previously written down. <br><br>I was encouraged by a fellow workshop participant to blog this one so here it is!<br><br><a class="" href="https://indieweb.social/tags/W3C" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">W3C</span></a> <a class="" href="https://indieweb.social/tags/credweb" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">credweb</span></a> <a class="" href="https://indieweb.social/tags/credibleWeb" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">credibleWeb</span></a> <a class="" href="https://indieweb.social/tags/authenticWeb" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">authenticWeb</span></a> <a class="" href="https://indieweb.social/tags/technology" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">technology</span></a> <a class="" href="https://indieweb.social/tags/technical" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">technical</span></a> <a class="" href="https://indieweb.social/tags/proposal" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">proposal</span></a> <a class="" href="https://indieweb.social/tags/technicalProposal" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">technicalProposal</span></a> <a class="" href="https://indieweb.social/tags/history" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">history</span></a></p>
Tantek Çelik<p>I just participated in the first W3C Authentic Web Mini Workshop<a href="https://tantek.com/2025/071/t1/w3c-authentic-web-workshop-flaws#t5az1_note-1" rel="nofollow noopener noreferrer" target="_blank">¹</a> hosted by the Credible Web Community Group<a href="https://tantek.com/2025/071/t1/w3c-authentic-web-workshop-flaws#t5az1_note-2" rel="nofollow noopener noreferrer" target="_blank">²</a> (of which I’m a longtime member) and up front I noted that our very discussion itself needed to be careful about its own credibility, extra critical of any technologies discussed or assertions made, and initially identified two flaws to avoid on a meta level, having seen them occur many times in technical or standards discussions:<br><br>1. Politician’s Syllogism — "Something must be done about this problem. Here is something, let's do it!"<br><br>2. Solutions Looking For Problems — "I am interested in how tech X can solve problem Y"<br><br>After some back and forth and arguments in the Zoom chat, I observed participants questioning speakers of arguments rather than the arguments themselves, so I had to identify a third fallacy to avoid:<br><br>3. Ad Hominem — while obvious examples are name-calling (which is usually against codes of conduct), less obvious examples (witnessed in the meeting) include questioning a speaker’s education (or lack thereof) like what they have or have not read, or would benefit from reading.<br><br>I am blogging these here both as a reminder (should you choose to participate in such discussions), and as a resource to cite in future discussions.<br><br>We need to all develop expertise in recognizing these logical and methodological flaws &amp; fallacies, and call them out when we see them, especially when used against others. <br><br>We need to promptly prune these flawed methods of discussion, so we can focus on actual productive, relevant, and yes, credible discussions.<br><br><a class="" href="https://indieweb.social/tags/W3C" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">W3C</span></a> <a class="" href="https://indieweb.social/tags/credweb" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">credweb</span></a> <a class="" href="https://indieweb.social/tags/credibleWeb" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">credibleWeb</span></a> <a class="" href="https://indieweb.social/tags/authenticWeb" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">authenticWeb</span></a> <a class="" href="https://indieweb.social/tags/flaw" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">flaw</span></a> <a class="" href="https://indieweb.social/tags/fallacy" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">fallacy</span></a> <a class="" href="https://indieweb.social/tags/fallacies" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">fallacies</span></a> <a class="" href="https://indieweb.social/tags/logicalFallacy" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">logicalFallacy</span></a> <a class="" href="https://indieweb.social/tags/logicalFallacies" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">logicalFallacies</span></a><br><br><br>Glossary<br><br>Ad Hominem<br>&nbsp; attacking an attribute of the person making an argument rather than the argument itself<br>&nbsp; <a class="" href="https://en.wikipedia.org/wiki/Ad_hominem" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/Ad_hominem</a><br><br>Politician's syllogism<br>&nbsp; <a class="" href="https://en.wikipedia.org/wiki/Politician%27s_syllogism" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/Politician%27s_syllogism</a><br><br>Solutions Looking For Problems (related: <a class="" href="https://indieweb.social/tags/solutionism" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">solutionism</span></a>, <a class="" href="https://indieweb.social/tags/solutioneering" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">solutioneering</span></a>)<br>&nbsp; Promoting a technology that either has not identified a real problem for it to solve, or actively pitching a specific technology to any problem that seems related. Wikipedia has no page on this but has two related pages: <br>&nbsp; * <a class="" href="https://en.wikipedia.org/wiki/Law_of_the_instrument" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/Law_of_the_instrument</a><br>&nbsp; * <a class="" href="https://en.wikipedia.org/wiki/Technological_fix" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/Technological_fix</a><br>&nbsp; Wikipedia does have an essay on this specific to Wikipedia:<br>&nbsp; * <a class="" href="https://en.wikipedia.org/wiki/Wikipedia:Solutions_looking_for_a_problem" rel="nofollow noopener noreferrer" target="_blank">https://en.wikipedia.org/wiki/Wikipedia:Solutions_looking_for_a_problem</a><br>&nbsp; Stack Exchange has a thread on "solution in search of a problem":<br>&nbsp; * <a class="" href="https://english.stackexchange.com/questions/250320/a-word-that-means-a-solution-in-search-of-a-problem" rel="nofollow noopener noreferrer" target="_blank">https://english.stackexchange.com/questions/250320/a-word-that-means-a-solution-in-search-of-a-problem</a> <br>&nbsp; Forbes has an illustrative anecdote: &nbsp;<br>&nbsp; * <a class="" href="https://www.forbes.com/sites/stephanieburns/2019/05/28/solution-looking-for-a-problem/" rel="nofollow noopener noreferrer" target="_blank">https://www.forbes.com/sites/stephanieburns/2019/05/28/solution-looking-for-a-problem/</a><br><br><br>References<br><br><a href="https://tantek.com/2025/071/t1/w3c-authentic-web-workshop-flaws#t5az1_ref-1" rel="nofollow noopener noreferrer" target="_blank">¹</a> <a class="" href="https://www.w3.org/events/workshops/2025/authentic-web-workshop/" rel="nofollow noopener noreferrer" target="_blank">https://www.w3.org/events/workshops/2025/authentic-web-workshop/</a><br><a href="https://tantek.com/2025/071/t1/w3c-authentic-web-workshop-flaws#t5az1_ref-2" rel="nofollow noopener noreferrer" target="_blank">²</a> <a class="" href="https://credweb.org/" rel="nofollow noopener noreferrer" target="_blank">https://credweb.org/</a> and <a class="" href="https://www.w3.org/community/credibility/" rel="nofollow noopener noreferrer" target="_blank">https://www.w3.org/community/credibility/</a><br><br><br>Previously in 2019 I participated in <a class="" href="https://indieweb.social/tags/MisinfoCon:" rel="nofollow noopener noreferrer" target="_blank">#<span class="p-category">MisinfoCon:</span></a> <br>* <a class="" href="https://tantek.com/2019/296/t1/london-misinfocon-discuss-spectrum-recency" rel="nofollow noopener noreferrer" target="_blank">https://tantek.com/2019/296/t1/london-misinfocon-discuss-spectrum-recency</a><br>* <a class="" href="https://tantek.com/2019/296/t2/misinfocon-roundtable-spectrums-misinformation" rel="nofollow noopener noreferrer" target="_blank">https://tantek.com/2019/296/t2/misinfocon-roundtable-spectrums-misinformation</a></p>
Fynn Ellie Becker<p>With WAI and WCAG 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> is arguably one of the biggest accessibility rights advocates out there.</p><p>W3C is also incorporated in the USA which seeks to abolish accessibility programs.</p><p>Asking the inconvenient questions:</p><p>Is W3C safe from Trump’s and Musk’s thug gangs currently overtaking the US government?</p><p>Is it time to consider moving the W3C to a less fascist place? I’ve heard the EU is still kinda ok. You might even consider going “true neutral” in Switzerland.</p><p><a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> <a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WCAG</span></a></p>
Bryan<p>These primitive APIs are why our system can be so stinking fast across 1,000s of elements on the page and none of this was possible in 2018 when I started to envision what we now call HAXcms.</p><p><a href="https://mastodon.social/tags/webdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>webdev</span></a> <a href="https://mastodon.social/tags/w3c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3c</span></a> <a href="https://mastodon.social/tags/web" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>web</span></a> <a href="https://mastodon.social/tags/dev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dev</span></a> <a href="https://mastodon.social/tags/developer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>developer</span></a> <a href="https://mastodon.social/tags/css" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>css</span></a> <a href="https://mastodon.social/tags/js" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>js</span></a> <a href="https://mastodon.social/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>html</span></a></p>
Mia (web luddite)<p>Since 2009, I've been contributing to open web tools &amp; standards,&nbsp;with a focus on CSS and related platform features at the W3C. But that work takes resources, making it hard for independent contributors like us <span class="h-card" translate="no"><a href="https://front-end.social/@OddBird" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>OddBird</span></a></span> to stay involved.</p><p>We need support. If you appreciate what we're doing, you (or your company) can sponsor our work directly:</p><p><a href="https://opencollective.com/oddbird-open-source" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">opencollective.com/oddbird-ope</span><span class="invisible">n-source</span></a></p><p>Let's keep building an open web for everyone.</p><p><a href="https://front-end.social/tags/w3c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3c</span></a> <a href="https://front-end.social/tags/css" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>css</span></a></p>
Thor A. Hopland<p>As you see there is plurality, but there is nothing easy about building a web engine. </p><p>Rendering HTML via DOM, implementing JS parsing, all the modern <a href="https://snabelen.no/tags/JS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>JS</span></a> standards, the <a href="https://snabelen.no/tags/HTTPS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>HTTPS</span></a> protocol, every <a href="https://snabelen.no/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> standard that hasn't been deprecated. It's a big, big task to build something like this.</p><p>Shout outs to <a href="https://snabelen.no/tags/Ladybird" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ladybird</span></a>. That slipped my mind completely, a bottom up rewrite - which is insane.</p><p>In any case, there are engines a plenty...</p><p>So why not build a browser?</p>
Rob Whitaker<p>A draft of ‘W3C Guidance on Applying WCAG 2.2 to Mobile’ is now available!<br>We’d really love your comments on the document in GitHub- we want to make sure these guidelines are clear for *everyone* who works on building mobile applications.<br><a href="https://iosdev.space/tags/accessibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>accessibility</span></a> <a href="https://iosdev.space/tags/a11y" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>a11y</span></a> <a href="https://iosdev.space/tags/w3c" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>w3c</span></a> <a href="https://iosdev.space/tags/wcag" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>wcag</span></a></p><p><a href="https://w3c.github.io/matf/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">w3c.github.io/matf/</span><span class="invisible"></span></a></p>
Steve Faulkner<p>👋🏽 Some people claim that something can't be done, then ignore feedback </p><p><a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> <a href="https://mastodon.social/tags/WCAG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WCAG</span></a> </p><p>🤔 </p><p><a href="https://github.com/w3c/wcag3/discussions/286#discussioncomment-12348435" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/w3c/wcag3/discussio</span><span class="invisible">ns/286#discussioncomment-12348435</span></a></p>
Luís de Sousa<p>1/2 The Spatio-Temporal Data on the Web Working Group (<a href="https://mastodon.social/tags/SDWWG" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SDWWG</span></a>) of the World Wide Web Consortium (<a href="https://mastodon.social/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a>) was recently re-chartered. The next two years I will be co-chairing this group with Rob Atkinson (<a href="https://mastodon.social/tags/OGC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OGC</span></a>).</p><p>There is a great deal brewing up in the <a href="https://mastodon.social/tags/GeoSemantics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GeoSemantics</span></a> space, to name just a few:<br>- <a href="https://mastodon.social/tags/SOSA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SOSA</span></a> 2.0 <br>- <a href="https://mastodon.social/tags/GeoDCAT" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GeoDCAT</span></a><br>- <a href="https://mastodon.social/tags/WebVMW" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>WebVMW</span></a><br>- An <a href="https://mastodon.social/tags/Ontology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Ontology</span></a> for Coordinate Reference Systems (<a href="https://mastodon.social/tags/CRS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CRS</span></a>)<br>- A <a href="https://mastodon.social/tags/3D" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>3D</span></a> extension for <a href="https://mastodon.social/tags/GeoSPARQL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GeoSPARQL</span></a></p><p>Join in!</p><p><a href="https://lists.w3.org/Archives/Public/public-sdw-wg/2025Feb/0002.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">lists.w3.org/Archives/Public/p</span><span class="invisible">ublic-sdw-wg/2025Feb/0002.html</span></a></p>
Carlo Gubitosa :nonviolenza:<p>In case you're lost, here is the map.</p><p>Source of the mindmap:</p><p><a href="https://www.w3.org/DesignIssues/Good.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="">w3.org/DesignIssues/Good.html</span><span class="invisible"></span></a></p><p><a href="https://sociale.network/tags/W3C" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>W3C</span></a> <a href="https://sociale.network/tags/TimBernersLee" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TimBernersLee</span></a> <a href="https://sociale.network/tags/ActivityPub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ActivityPub</span></a></p>