Jan Alexander Steffens

I just checked this again (using the current neqo e71e860489447fed25b64bd8ec31a804dccb0dad compared to curl 7.85.0), and the performance of H3 is still extremely poor, though this time H3/IPv6 is much slower...

The old code also removed the chains that `_materialize` adds to the `chains` from the `chains_to_fetch`. Is this behavior covered again?

It looks like the refactoring missed that the chains added by `_materialize` to the `chains` dict should be removed from `chains_to_fetch`, so I guess it keeps requesting the same chains...

I've also partially reverted #17044 with apparent success. This is the diff: Diff ```diff diff --git c/synapse/storage/databases/main/event_federation.py w/synapse/storage/databases/main/event_federation.py index fb132ef09..97ac07c3a 100644 --- c/synapse/storage/databases/main/event_federation.py +++ w/synapse/storage/databases/main/event_federation.py @@ -280,16 +280,64 @@ class...

Before this was fixed (for a while) I used to work around this by hacking the HTTP agent for preview requests to be `curl/7.84.0` (or whatever was current). That got...

Here's a script that should output a Synapse-compatible `providers.json`: ```python #!/usr/bin/env python3 import json from collections import OrderedDict from sys import stdout from urllib.parse import urlparse import jsonschema import requests...

It's not disabled. The module is available.

It would be nice if `AWAY` on the IRC side was synced with presence on the Matrix side, in both directions.

It should be `vsnprintf`. ```c int vsprintf_s(char *buffer, size_t numberOfElements, const char *format, va_list argptr); int vsnprintf(char *restrict str, size_t size, const char *restrict format, va_list ap);

Also `stricmp` and `_stricmp` should probably be `strcasecmp`, not just `strcmp`.