@sen @headcrack Unless I'm horribly mistaken, that's an entirely separate timeout. I.e. for the daemon->subprocess. The subprocess on its own has its entirely own timeouts for each individual instruction it runs.

Also, if this is supposed to relate to the hash.my ordeal, it doesn't explain why CURL as a backend handles it perfectly fine while PHP sockets don't.

Also I have run tests entirely separate of the !GNUsocial framework and can recreate the issue of inconsistent timeouts with PHP sockets: https://git.gnu.io/gnu/gnu-social/issues/281#note_5674