I am again reminding y’all not to auto-fail regions / landmarks that have no accName:
adrianroselli.com/2024/06/mayb…
I am also begging y’all to stop using `aria-label`:
• adrianroselli.com/2019/11/aria…
• ericwbailey.website/published/…
If you aren’t testing in screen readers (not just VoiceOver or ChromeVox) then please just stop already.
aria-label Does Not Translate
As of my 28 January 2024 update at the end of this post, aria-label auto-translation support is seemingly as spotty as when I first wrote this post. It does, actually. Sometimes.Adrian Roselli
daniel:// stenberg://
in reply to daniel:// stenberg:// • • •jordan
in reply to daniel:// stenberg:// • • •somehybrid
in reply to daniel:// stenberg:// • • •Stefan Eissing
in reply to daniel:// stenberg:// • • •LisPi
in reply to daniel:// stenberg:// • • •That sounds mildly sarcastic.
I'm not convinced shoving yet another nontrivial protocol into ambient-authority land is advisable.
daniel:// stenberg://
in reply to LisPi • • •@lispi314 I agree that's worthwhile discussion. There are certainly both pros and cons with both ways: userspace and kernelspace.
I don't think a full QUIC implementation will be accepted into the kernel anytime soon though because of its complexity.
Steven Reed
in reply to daniel:// stenberg:// • • •EricJ
in reply to daniel:// stenberg:// • • •I mean... I kind of like it. IPPROTO_QUIC added to ye olde socket API looks neat/simple to me, and (as a transport layer) I think it belongs in the kernel anyway.
I assume you prefer QUIC in userspace? For portability reasons?
daniel:// stenberg://
in reply to EricJ • • •Richard Levitte
in reply to daniel:// stenberg:// • • •My thought: oh, it's finally happening.
I've been expecting this for a while...