Very interesting thoughts on how to collectively fund and decide on basic tech infrastructure
https://bkardell.com/blog/Breakouts2025.html Context: #W3C, #freesoftware, web browsers, @igalia
Very interesting thoughts on how to collectively fund and decide on basic tech infrastructure
https://bkardell.com/blog/Breakouts2025.html Context: #W3C, #freesoftware, web browsers, @igalia
@lozross @tibosl @tibhannover very nice! it looks like the #TS4NFDI project is closely aligned with the aims of the #reconciliation #W3C community group (https://www.w3.org/community/reconciliation/) and its protocol (https://www.w3.org/community/reports/reconciliation/CG-FINAL-specs-0.2-20230410/) - do you know if there is awareness of this protocol and any plans to do something with it?
#Development #Proposals
How do we evolve CSS logical shorthands? · There are options, but one major roadblock https://ilo.im/1630tm
_____
#CSS #Shorthand #LogicalProperties #Specification #CSSWG #W3C #WebDev #Frontend
#Development #Announcements
CSS Mixins are ready to explore · How you can enable the feature in Chrome Canary https://ilo.im/162zz3
_____
#ModernCSS #W3C #Specification #CssMixins #CssFunctions #Chrome #Browser #WebDev #Frontend #CSS
>> Twenty-five years ago I was part of an effort… to develop a standard environment for the exchange of business documents called #ebXML. It was an open-standards internet follow-on to #EDI. … an environment in which all the actual business transactions were between machines, without the need for human…
Then, @timbl and #W3C invented the #SemanticWeb and #OWL reasoners, which I can't help but see as a precursor to the current AI push, and a continuation of that way of thinking
The Tor Project is actually verified from torproject.org...including Mullvad being verified too...
EFF is too!(verfied too!)
torproject@mastodon.social
mullvadnet@mastodon.online
eff@mastodon.social
mastodon.archive.org
Then archive.org even cooler They are on the fediverse with their own instance!!! So is w3c!
w3c@w3c.social
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):
When you are looking at implementing the current W3C recommendation to sign documents, and you need to travel to the future, 6 days.
When you are looking at implementing the current W3C recommendation to sign documents, and you need to travel to the future, 6 days.
Something I wrote in the W3C Authentic Web Mini Workshop’s Zoom chat:
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.
A technical proposal should not be praised for what it claims to solve.
A technical proposal must be evaluated by what marginal difference or advantage does it provide over existing technologies.
Any technical proposal that ignores prior technologies is itself doomed to be ignored by the next technical proposal.
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 & forth can help inspire summarizing of points which one had not previously written down.
I was encouraged by a fellow workshop participant to blog this one so here it is!
#W3C #credweb #credibleWeb #authenticWeb #technology #technical #proposal #technicalProposal #history
I just participated in the first W3C Authentic Web Mini Workshop¹ hosted by the Credible Web Community Group² (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:
1. Politician’s Syllogism — "Something must be done about this problem. Here is something, let's do it!"
2. Solutions Looking For Problems — "I am interested in how tech X can solve problem Y"
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:
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.
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.
We need to all develop expertise in recognizing these logical and methodological flaws & fallacies, and call them out when we see them, especially when used against others.
We need to promptly prune these flawed methods of discussion, so we can focus on actual productive, relevant, and yes, credible discussions.
#W3C #credweb #credibleWeb #authenticWeb #flaw #fallacy #fallacies #logicalFallacy #logicalFallacies
Glossary
Ad Hominem
attacking an attribute of the person making an argument rather than the argument itself
https://en.wikipedia.org/wiki/Ad_hominem
Politician's syllogism
https://en.wikipedia.org/wiki/Politician%27s_syllogism
Solutions Looking For Problems (related: #solutionism, #solutioneering)
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:
* https://en.wikipedia.org/wiki/Law_of_the_instrument
* https://en.wikipedia.org/wiki/Technological_fix
Wikipedia does have an essay on this specific to Wikipedia:
* https://en.wikipedia.org/wiki/Wikipedia:Solutions_looking_for_a_problem
Stack Exchange has a thread on "solution in search of a problem":
* https://english.stackexchange.com/questions/250320/a-word-that-means-a-solution-in-search-of-a-problem
Forbes has an illustrative anecdote:
* https://www.forbes.com/sites/stephanieburns/2019/05/28/solution-looking-for-a-problem/
References
¹ https://www.w3.org/events/workshops/2025/authentic-web-workshop/
² https://credweb.org/ and https://www.w3.org/community/credibility/
Previously in 2019 I participated in #MisinfoCon:
* https://tantek.com/2019/296/t1/london-misinfocon-discuss-spectrum-recency
* https://tantek.com/2019/296/t2/misinfocon-roundtable-spectrums-misinformation
With WAI and WCAG the @w3c is arguably one of the biggest accessibility rights advocates out there.
W3C is also incorporated in the USA which seeks to abolish accessibility programs.
Asking the inconvenient questions:
Is W3C safe from Trump’s and Musk’s thug gangs currently overtaking the US government?
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.
Since 2009, I've been contributing to open web tools & standards, 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 @OddBird to stay involved.
We need support. If you appreciate what we're doing, you (or your company) can sponsor our work directly:
https://opencollective.com/oddbird-open-source
Let's keep building an open web for everyone.
A draft of ‘W3C Guidance on Applying WCAG 2.2 to Mobile’ is now available!
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.
#accessibility #a11y #w3c #wcag
Some people claim that something can't be done, then ignore feedback
https://github.com/w3c/wcag3/discussions/286#discussioncomment-12348435
Check out this "Comprehensive #Accessibility #Checklist for Web Projects" by the @a11ycollective. It's a good start for start for your journey into accessibility on the web...
#WCAG #W3C #WAI #BITV
https://www.a11y-collective.com/blog/accessibility-checklist/
In case you're lost, here is the map.
Source of the mindmap:
The #W3C has a WAI effort, which really stands for "Web Accessibility Initiative", but I always read it as "Working As Intended".
https://www.w3.org/WAI/