News for hackers. Stuff that matters.

otbutz

Re:HTTP/2 and HTTP/3 explained on Thursday March 14, 2024 @04:56AM (#39701692)
> HTTP/3 was designed for unstable connections, such as cellphone and satellite networks.

Satellite networks are not a good example. Regular HTTP/1.1, paired with a PEP, outperforms HTTP/3 by an order of magnitude.

Re:Freenginx: Core Nginx developer announces fork on Thursday February 15, 2024 @04:18AM (#39380621)
The issue you linked to is an excellent example of why everyone and their dog is becoming a CNA these days. It's the only way to keep CVE spam at bay. The system has been broken by the gamification of CVEs and is in desperate need of reform.
Re:Filecoin Foundation Successfully Deploys IPFS in Space on Tuesday January 16, 2024 @10:11AM (#39014099)
Isn't the QUIC transport the default since v0.6.0? Compared to TCP, it's much better suited for satellite communications.
Re:Curl on track for non-experimental HTTP/3 support on Monday October 16, 2023 @08:59AM (#37899236)
Anything that involves high latency and/or packet loss. And in general: testing servers.

The question is also a bit odd, to be honest. There's no need to look for a beneficial use case to add support for the next iteration of the HTTP protocol.

Re:Syncthing: A continuous file synchronization program on Wednesday May 10, 2023 @05:28AM (#35885351)
You could try to force QUIC which should handle latency a bit better. The priority of TCP/QUIC will be configurable with the upcoming v1.23.5 release:

https://github.com/syncthing/syncthing/pull/8868

That would be great! I've only had a quick look at the docs, but the API seems reasonable:

https://docs.joinmastodon.org/methods/apps/oauth/ https://docs.joinmastodon.org/methods/statuses/

OT but i wish they'd add Mastodon support.

https://github.com/caronc/apprise/issues/586

Re:Pingora, the proxy that connects Cloudflare to the Internet on Friday September 16, 2022 @07:41AM (#32864776)
There is quic-go[1] but i don't think that it's sufficiently optimized[2-4] to be used for this kind of workload. caddy will use it to provide HTTP/3 by default[5] in the upcoming 2.6.0 release.

[1]: https://github.com/lucas-clemente/quic-go [2]: https://github.com/lucas-clemente/quic-go/issues/2877 [3]: https://github.com/lucas-clemente/quic-go/issues/2607 [4]: https://github.com/lucas-clemente/quic-go/issues/341 [5]: https://github.com/caddyserver/caddy/pull/4707

I have also been struggling lately with prepared statements and obscure query planning decisions. The developers of the mssql JDBC driver seem to be determined to force the use of prepexec in their driver, which causes high execution times for typical ORM-generated queries:

https://github.com/microsoft/mssql-jdbc/issues/1196