@jpegxl Will #jpegXL need additional metadata when used with HTML's srcset?
While the format's progressive rendering can do away with the need to have different files per resolution, browsers will instead need to know how much of the image they'll fetch. How would we pass that information to the browser?
Extra syntax in srcset, eg p.jxl, p.jxl \<2040 100w, p.jxl \<6974 200w to tell that for a 100px wide view the browser needs to load the first 2040 bytes? Fragment identifier tricks?
The very same type of mistakes happens in file systems even without URIs being involved. Directory traversal checks look simple but sooner or later need hard-to-understand symlink following rules. Enforcing processor policy has terrible portability there (it even only became practical on Linux with landlock), but nonetheless I think it's preferable.
Not mixing URI parsers is a good advice for when processor policies are unavailable – but let's try to make them available more often.
@snaggen I think the better lesson than "don't mix URI parses" here is "don't LBYL, rely on EAFP". Many "Look before you leap" (LBYL) schemes are subject to variations of time-of-check/time-of-use errors. It's preferable to not sanitize input, but tell the processor what the policy on processing is; when it comes to a violation, it's easier to ask forgiving (i.e. report the error) than permission (EAFP).
@0xsaksham @snaggen Last polls I saw, the #RustLang hashtag (it's case sensitive, but capitalization helps for accessibilisy) was a tad more popular than #Rust due to the latter's ambiguities.
@jvisick That process is completely intransparent to anyone approaching this without preexisting knowledge of that Lemmy instance. Do you know who runs that account? They should really make a note in its metadata.
Last time I checked, GTK could do laziness well where it matters (lists /trees), but admittedly that was some time ago.
chrysn @chaos.social Technology enthusiast with a focus on Free Software and embedded systems. Science fiction promised us general purpose electronics, let's build them! (And get their security properties right.)