ximm

I also think these are very similar. The main difference in my view is that the state parameter is checked by the client, while PKCE is checked by the server.

I run an authentication server and requiring PKCE allows me to make sure that XSS protection is handled for all clients.

> For coders, visual aesthetics don’t matter. For lawyers, they are a technical requirement. While this difference may seem arbitrary on the surface, it is downstream of a critical technical difference between the two fields. Machines interpret the work of coders. Human institutions interpret the work of lawyers.

I believe this is not only infuriating, I am pretty sure it is actually illegal. If lawyers would think that visuals are more important than semantics, they would explicitly discriminate blind people.

100% this. When I reached the end of that page I felt pranked because the obvious question was never answered. How are these cases resolved? Is it possible to fix some inputs and only update others? What if I sometimes want to change input A, and other times I want to update input B? All this should be explained as early as possible.

Last time I checked hyprland was pretty much despised in the wider linux developer community. See for example https://drewdevault.com/2023/09/17/Hyprland-toxicity.html. Has anything about that changed?

There is no real difference between ratio and difference. It is just scaled with a logarithm. See https://blog.ce9e.org/posts/2022-09-10-contrast-algorithms/ for details.

Any reference to APCA has been removed from the WCAG 3 drafts in 2023 (see https://github.com/w3c/silver/commit/d5b364de1004d76caa7ddc4...).

I am not sure what the status is.

> Hundreds of thousands of cars physically move along roads and have to break, accelerate and change lanes in traffic to safely get to their destination. Future work: Other modes of transport (pedestrians, light & heavy rail, airports, etc.). Multi-modal pathfinding (combining walking, public transport, taxis and driving to reach destinations).

So this is a US simulator.

What are the UN Open Source Principles? Can anyone share a link to the original document? I could not find anything relevant on Google.

Damn, I had planned to go shopping on that day!

Client must provide a proof-of-work. There is no standard for that, so the only way is to implement the client-side code in javascript.

It would be great if there was a standard for that so that all kinds of clients knew how to provide a proof of work, e.g. like this:

  WWW-Authenticate: Proof-Of-Work difficulty=5 challenge=XYZ
  Authorization: Proof-Of-Work abc

Where sha256(abcXYZ) would have to start with at least 5 zeros.

Webauthn always requires a user presence check though.

There was the "Do Not Track" header, but I don't think any sites that actually honored it. And it is deprecated now.

On Firefox we still have webRequestBlocking, so it is quite simple to block cookies. See for example https://addons.mozilla.org/en-US/firefox/addon/ximatrix/

Nice use of the ch and lh units!

This looks nice, but I fail to see any use cases that cannot be handled with bwrap and mount namespaces.

> have a theory that every major technology shift happened when one part of the stack collapsed with another.

If that was true, we would ultimately end up with a single layer. Instead I would say that major shifts happen when we move the boundaries between layers.

The author here proposes to replace servers by synced client-side data stores.

That is certainly a good idea for some applications, but it also comes with drawbacks. For example, it would be easier to avoid stale data, but it would be harder to enforce permissions.

I agree, but at least it is consistent. This is also how `for`, `list`, `aria-labelledby`, `aria-describedby`, and probably many other attributes work.

This is a nicely written description of some of the things that flatpak does under the hood for people who know docker. Of course, flatpak does a lot more (e.g. filtered dbus access).

I personally think that flatpak is not the end of history and we should continue to experiment with different approaches.

The one thing I thought was IMHO missing from this article was JavaScript.

In HTML, it is pretty natural to add white space (i.e. text nodes containing white space) between all elements. You basically only have to worry if you want to avoid that.

In JavaScript, the opposite is true. If you want to create a text node, you have to do so explicitly. If you just create elements and append them to the same parent, they will be added without whitespace.

I am not sure how JSX behaves in this regard. Last time I checked it was more like JavaScript than HTML, which was of curse very confusing for people.

Concerning text-to-speech and the missing separation of HTML and CSS: There are several open issues about this in the spec that defines how accessible names and descriptions are computed from HTML elements: https://github.com/w3c/accname/issues?q=state%3Aopen%20label...

I expected an uninformed rant and actually got a really well informed, balanced rant. I don't agree that this is a major issue, but every time I thought of a counter argument it was immediately addressed in the article. Well done!

If you love it so much, here is another one: https://blog.ce9e.org/posts/2025-01-07-oidc/

I prefer using language agnostic tools where possible because that is both simpler and allows me to use the same tools with every language. For example, git, grep, or vim all work on any text file. vim has a few language specific settings though (e.g. syntax highlighting).

I have an alias for `vim -p $(git grep -li "$1") +"/$1"` that allows me to quickly open files that contain a given string.

Making energy expensive is kind of the point, isn't it? The cost of destroying the planet was not billed in so far, so we need to correct that.

For context: Losing this vote was intended. The government already fell apart in November, so this is the next formal step towards new elections.

I never really understood why people want to style stuff like this. I like how you can express yourself by using colors and layout and stuff like that. But at some point usability is more important than branding.

ding ding ding we have a godwin

Friendly reminder that inline CSS is unsafe and should be avoided. https://stackoverflow.com/questions/41925390

One thing we I wish we would do with these tools is separate all the aria logic from the UI. We should put all that complex aria stuff into a library and then build different UIs on top of a shared, well tested code base.

Shameless plug: https://github.com/xi/aria-api

I noticed that I automatically switched to only reading headings when the sections were super short. I guess there is some kind of rule here: The more headings you use, the less people will read your paragraphs.