This is bullshit, I'm done with Caddy. It's burned me so many times. They keep shipping half broken shit like their HTTP/3 support that is enabled by default (currently broken in releases because it sends duplicate Content-Length headers)
I'm switching to Apache LMAO. It's gonna be 95% the speed of Nginx and they ship mod_md in their Docker images so it can handle fetching its own Acme certs
For the five thousandth time, NO, it is not. It sucks. The XEPs suck. The clients almost all universally suck except like *one* client on Android. The server hosting story is an overcomplicated mess.
@p@silverpill@frogzone@jeffcliff We'll do ed25519 if it's gonna actually stick. I don't think it's been revisited since the original proposal was seen and I didn't even know Honk was supporting it.
@p@mint@j All the IO stuff in BEAM/Erlang/Elixir is written in C. Same with the networking stuff like the TCP/UDP functionality, cryptography, JSON in latest OTP release, etc
@p@j@mint I think this would be achieved with Stream.reduce or one of the other Stream functions. All IO related stuff (anything unixy exposed as a file, network stuff, etc) can be streamed. It obviously would've be as efficient as C because after so many reductions (function calls, mostly. Stream internally is gonna be calling itself in a loop reading chunks) it will be preempted and another process would get to run
@p I spent so many hours fighting with IPFS I think it's a dead end. You can even find a stale MR where I upgraded the storage backend from Badger to Badger2 (because the default filesystem store sucks) and it didn't help much. Nobody working on Kubo has any interest in fixing the storage scalability problems it seems. To use it for fedi we'd really want the garbage collection to work and not spin 100% CPU and IO for hours but that's what it does when you get enough data in there 🤬