@bkardell visits the Fireside

"Brian works at Igalia, he is a member of the W3C Technical Architecture Group (TAG). He also paints many and varied subjects and writes thoughtfully about Web Standards."

https://html5accessibility.com/stuff/2026/06/11/brian-kardell-visits-the-fireside/

#accessibility #webStandards #W3C #WHATWG #Igalia

Brian Kardell visits the Fireside – HTML Accessibility

Ehem, #JavaScript also uses the backslash as a separator in the URL.pathname, like '/'. Firefox dev console, but node is similar:

% let a = new URL("http://localhost/abc\\def")
> undefined
% a.pathname
> "/abc/def"

Can anyone point to a spec where this is described?

#mdn #whatwg

The Website Specification

A platform-agnostic, full specification of the technical features a good website should have. Built in the open under an MIT licence.

The Website Specification

ROTFL

#Rust core team listens to Rust developers like the #GAFAM-controlled #WHATWG listens to web developers

#LLM #XSLT #genAI

Someone filed an issue with WHATWG (the people that influence how standards are adopted by the major web browsers) in which they proposed a standard way to disclose the use of AI through HTML metadata:

Proposal: Meta Tag for AI Generated Content #9479

This led to the creation of the AI Content Disclosure Community Group, which has some initial members but has yet to choose a chair.

These groups are typically organized on Github, so I went to see what had been done so far on their repository.

Their repo is less than a month old and has very few committers, but it already includes contributions from claude, and this was only disclosed because I manually blocked the claude account through my github accounts settings.

They are not off to a great start.

#AI #claude #WHATWG

@[email protected]
And all of this starts with the data itself.
Code is data. Data is code.

#GDPR lack of enforcement against US #BigTech shows that while you are right at a theoretical level, in practice we need to be extremely careful to not be fooled by lobbyists that work to replace law with "paper compliance".

It would be easy for a US company to argue they produce open source, with open formats and open API defined by "open standards" that they control.

Then, to keep everything unchanged, they might just take competitor out of the market with overwhelming complexity, unfair competition based on free tiers and by buying the few survivors (if any).

Forced interoperability might be a step further, but it's not enough anyway: both #Meta and #BlueSky interoperate with the #fediverse over #ActivityPub, but in fact they jusr harmed the fediverse without any user moving over here preserving their contacts.

In brief, to get Digital Sovereignty we need to get rid of US tech.

There is no alternative, only procrastination.
They key point is that source code must be open and available for all.  That takes away the chances of someone talking full control of the software and restricting the freedom otherwise possible.
I'd love if it was that simple!
Unfortunately, it's not.

Again, #Chromium is open source and its code is available for all.
Yet it's tightly controlled by #Google that shape it (and the #WHATWG "open standards") into one of the worse and most powerful surveillance and manipulation tools out there.

I agree that some #opensource projects might be useful to gain #DigitalSovereignty (think of #NextCloud for example), but only if when their development is not controlled by any corporation tied with external governments.

This cut out all biggest open source projects, mostly leaded by US corporations or their employees.
data in an open standard is another piece in the same puzzle.
Again, it's not so simple: for example both #OpenDocument and #OOXML (#OfficeOpenXML) are open standards, but in fact when you save in ooxml (docx, xlsx..) by #Microsoft tools, they include undocumented proprietary extensions that #LibreOffice cannot handle properly.

So again while proprietary formats always harm individual freedom and #DigitalSovereignty of nations, openness is not, by itself, enough to get them.

And yet, a proprietary format developed by a fully European company would harm individual freedom just like any proprietary format but, given the company would be only and fully subject to European law (no #FISA702, no #CLOUD Act, no #Trump...), it would still enhance the digital sovereignty of the Union over an open standard totally controlled by US corporations.

So things are more complex and you can't get any real freedom or sovereignty from buzzwords like "open", "free" or #foss.

So again, to get #digital sovereignty, first of all we need to be laser focused on getting rid of #US control over #UE computing, citizens and lawmakers.

Some Free Software and Open Standards may help achieving such goal, but just being open is not enough. And we can't wait for all european software to be free to achieve Digital Sovereignty.

@[email protected]
Contra Chrome – a webcomic – How Google's browser became a threat to privacy and democracy

@[email protected]
If you're concerned about the US controlling open source - you can fork it.
This is a naive take: above a certain complexity, hard forks of a software is not licensing issue. So while you can legally fork #Chromium, nobody can really hope of doing so in any meaningful way.

#WHATWG standards are dictated by the most used browsers, that are all US controlled anyway. And that's why it's such a monoculture, with #Firefox there only to provide a little #antitrust warranty to #Google: the standard themselves are designed to work as entry barriers to the browser market.

So again, open standards do not provide #DigitalSovereignty by themselves.

Open source and open standards only work in this regards whene there are several independent implementation from each country, so that there is no way to lock-in users, companies and countries' administrarions.

Without existing, multiple alternative, independent and fully interoperable implementations, open standards just reinforce centralization as Google proved when even #Microsoft abandoned their browser engine.

Then sure, #FreeSoftware helps with Digital #Sovereignty, since (and as long) people's #freedom is its primary concern.

But it's important to not conflate individual freedom and autonomy with digital sovereignty!

If all of your country payments are handled by US corporations, you might well use #GNU/#Hurd on your open hardware, but you are not free and your country has no sovereignty.

If all of your health data are stored by US corporations, they might well only use free software on open hardware located in your neighbourhood, but they are alware at a ssh of distance from #NSA, so you are not free and your country has no sovereignty.

What about your judges or your lawmakers exchanging unencrypted emails over #gmail or #outlook365?
Again, they can use opensource only, but you are not free, your country has no sovereignty and your vote is worth nothing.

So sure, after getting rid of US Tech we might even move to a #FOSS only stack EU-wide.

But first and foremost we need to break free from US control and surveillance.

Some opensource projects may help to ackieve this urgent goal.
Biggest ones won't and we shouldn't naively argue that going full opensource is per se useful or required to gain #DigitalSovereignty.

@[email protected]

Have you folks noticed how the recent stream of #JavaScript-related security issues in browsers has NOT resulted in a call from #Google to expunge #JS from the “web platform” as it was done for #XSLT?

#WHATWG #hypocrisy #hypocrites #openWeb #indieWeb

This, by the way, is the reason why my response to the news of the #WHATWG moving forward with the forced removal of #XSLT is

DO NOT COMPLY

https://wok.oblomov.eu/tecnologia/google-killing-open-web-2/#do.not.comply.

(I'll add to that: visit XSLT-using websites often. Blow those stats.)

Google is killing the open web, part 2

Do not comply in advance.

wok

For starters, most of what the #WHATWG is working on is largely irrelevant for the “web of documents”. This means largely no development efforts to “run after the latest revision of the spec”. I would expect most of the work to be of the maintenance kind (fixing bugs, security issues, and the like), which is sadly the kind of brutal, unglamorous work nobody wants to do.

22/