Christian Korneck

same for me, I tried but [it didn't seem to work](https://github.com/docker/hub-feedback/issues/2127#issuecomment-1152831106). Does this work for anyone here? If so, I'd appreciate a pointer into the right direction.

this would be extra useful as a Twitter Spaces recording only lives for 30 days, afterwards it's lost.

> If someone can provide an example that actually works, I can try to fix this [link](https://twitter.com/i/spaces/1OdKrBnaEPXKX?s=20)

@89z > If some "Twitter Spaces" is available for a short time after the live period is over, then I can work on that. I believe it's possible for the...

@89z > If Twitter Spaces cant be recorded "by any user", then how was the recording created that you linked to [1]? It appears that "Andrew Brown" is a user...

> I believe I have implemented this now awesome!

> @89z If you can find an example that works, that's three months or older, then I will restore and maintain the Twitter Spaces code your code works just fine...

There are currently no `docker-pushrm` flags that you could set to trust a custom server certificate or allow insecure connections. You could however add the public cert of your server...

> maybe this could be a feature request? Sure. Are there any particular reasons why making the self-signed cert trusted on the machine where you want to run docker-pushrm isn’t...

thanks, these are good thoughts, I will keep this open as a feature request