Christoph Spang

Thanks for your quick reply. I agree that there is a convenience/ security trade-off and my proposed default settings might be too weak for some use-cases (and therefore could be...

Environment: I observed a very similar bug on an iPhone 6s with prosody 0.12.0 using [cloud_notify_extensions](https://modules.prosody.im/mod_cloud_notify_extensions.html) on a nixos server. Bug description: After being offline (and eventually successfully receiving some...

- Bug also occurs when `mod_cloud_notify_extensions` is disabled. So should be unrelated to it. - Bugs seems unrelated to prosody version as it occurs with prosody 0.11.4 and 0.12.0. -...

Okay, here my findings: - This is very likely _NOT_ a bug in Siskin. - Siskin just used my very own faulty DNS Server Records, thus failed to RE_Connect -...

With the current information, this is just guessing. - Could you generate relevant (verbose) logs in siskin and/or server-side? Else: Could you provide your server configuration? To enable `$someone` to...

Next Guess: Push notifications are broken in the server configuration, synchronization fails at re-connect. Do push notifications work in your setup?

Alternative: How to manually construct and send the specifically needed post request? What I tried so far: `curl --data "url=https://myurl.com" https://api.movim.eu/pods/register` Maybe that worked... I will keep you updated. Hint:...

Behaviour: Movim daemon crashes ~once/ twice per day, this error might be related Setup: Debian 10, Nginx, PHP 7.3, current git movim version Log: `movim.ERROR: Trying to get property 'presence'...

Cross-reference to frigate: https://github.com/blakeblackshear/frigate/issues/2348

I am getting a similar error without touching the bank configuration, by just increasing the memory size of the single port tiny example to an arbitrary (?) size. Here is...