On Sun, Jun 02, 2024 at 01:18:28AM +0200, Steffen Nurpmeso wrote: > Thomas Dickey wrote in > <zluz447780sh4...@prl-debianold-64.jexium-island.net>: > |On Sat, Jun 01, 2024 at 07:59:07PM +0200, Steffen Nurpmeso wrote: > |> Thomas Dickey wrote in > |> <zlpf6rz52lw3a...@prl-debianold-64.jexium-island.net>: > |>|The current version of lynx is 2.9.2 > |> ... > |>|* adapt special case of gzip decompression in 2.8.9dev.12 to brotli, \ > |>|to handle > |>| downloads from websites which support "br" (report by Rajeev V \ > |>| Pillai) \ > |> ... > |> > |> That made me look .. i see IsCompressionFormat() does not handle > |> the zstd that is more and more used in the open source software > |> world, for package formats etc, and supported by webservers, too > |> (ie the wonderful lighttpd i use since 1.4.59 in 2021). > | > |actually - for websites so far, this seems to be used only by facebook/etc. > | > |I did notice it, considered whether to delay another week to do this. > | > |But since I'm not aware of any useful websites relying upon zstd, > |I put it off for "soon" (patches will be duly considered). > |It also would help to see websites using the feature. > > I now looked around a bit, and found > > https://bugzilla.mozilla.org/show_bug.cgi?id=1301878#c62 > > > It's probably worthwhile to mention that Chrome now supports > this behind a developer flag in 117 > (https://chromestatus.com/feature/6186023867908096). Given the > widespread industry support for Zstd at this point it seems very > likely that they'll keep the feature in. > > and #c65 > > Mozilla’s position on Zstandard for Content-Encoding changed > from “defer” in 2019 to positive in 2023. > > > https://github.com/mozilla/standards-positions/issues/105#issuecomment-566719336 > > > https://github.com/mozilla/standards-positions/issues/775#issuecomment-1754635490 > > and #c71 > > I think this can be closed? zstd support landed in v126: > https://www.mozilla.org/en-US/firefox/126.0/releasenotes/. The > devtools don't support it yet (responses just look like > gibberish) but that should be fixed by #1891610
sure - that tells us that chrome and firefox support the feature.
But I don't see any mention of websites using the feature.
> Oh wow, that is now amazing, that was nine days ago!
> By sheer coincidence.
>
> |2.9.2 is basically fixes prompted by feedback from 2.9.1 :-)
>
> 2.9.1 just works here.
>
> |> Would you be interested in adding support for that?
> |> If i write a patch?
> |
> |sure - there's enough in Lynx now for gzip and brotli that the patter \
s/patter/pattern/
> |should
> |be easy to follow.
>
> Yes i had that same impression; 'never have used it on programming
> level, but only looked a month ago (plzip related) and found
> unfortunately obsoleted user-passes-buffer interface variants, if
> i recall correctly.
for instance
ZSTD_DEPRECATED("Replaced by ZSTD_getFrameContentSize")
ZSTDLIB_API
unsigned long long ZSTD_getDecompressedSize(const void* src, size_t srcSize);
ZSTDLIB_API size_t ZSTD_decompress( void* dst, size_t dstCapacity,
const void* src, size_t compressedSize);
(like brotli, its developers weren't very interested in portability)
> I unfortunately have lost six months for my mailer due to writing
> a RFC 5322 parser (that i hope to integrate there however), and
> a DKIM signer, and talking loud on IETF lists that do not want to
> hear that .. anyway, eh, i cannot promise i find time next week or
> so, but i *would* come back to this issue, as i think it surely
> will make its way.
ttyl
--
Thomas E. Dickey <dic...@invisible-island.net>
https://invisible-island.net
signature.asc
Description: PGP signature
