mmahmad

This is very useful! I had an application that needed an async backend for a data processing pipeline in GCP but missed the familiarity of AWS Step Function + Lambda. This setup would have been a great replacement for that.

They say it doesn't solve the problem

- "Would adding federation to Signal help with users behind country-wide blocks? Seems like a distributed service would be harder to censor than a centralized one."

- "It's trivial to block several distributed hosts simultaneously. An aspiring censor would simply find the most common federated endpoints for a given service and block all of them. Only the users of that software would be affected. There wouldn't be any collateral damage. If the censors somehow didn't hit every single worthwhile federated endpoint, users would still be left wondering why they couldn't communicate with most of their friends. Moving between federated hosts would also necessitate an entirely new identifier, so users would need to rebuild their social graph again.

In addition to being ineffective against censorship, there are several other properties and trade-offs that make federation a difficult proposition for an application like Signal: https://signal.org/blog/the-ecosystem-is-moving/"

src: https://news.ycombinator.com/item?id=16868564

In a video chat between Andrew Ng and Hinton (part of Deeplearning.ai course), Hintom himself confirms this.

I'm curious as to how you manage the mirror. Do you perform all operations twice (e.g. if you push to Github, do you manually push to Gitlab)?

Edit: Nvm, found out Gitlab has the mirroring feature (https://docs.gitlab.com/ee/workflow/repository_mirroring.htm...). Pretty cool!