4 ms·

How would you start a chat with someone on the central server if the central server refuses any communication with the federation you're on?

• godelski 6y ago
  I guess there's something I'm missing here. I understand it is phone -> Signal server -> other phone. So don't you only need to know how to talk to the Signal server? Which should be in the OS app? So your app would just need to know which server to communicate with the right person. People that are on the Signal server get contacted through the Signal server. People on a federated server get communications passed through there. I'm sorry if this is a dumb question. I'm really curious but I don't know much about this space. What is Signal doing that restricts you from talking to it?
  • acct776 6y ago
    Not allowing incoming connections from anything besides their signed app.
  • infogulch 6y ago
    Signal probably ties message encryption to client authentication. You could give the 'federated' server your plaintext and encryption keys which acts like a client app on your behalf, but that obliterates the purpose of Signal and E2E messaging entirely. And still, they can ban your server IP at any time at their discretion. Maybe you can try to create a federated server that acts as one user but publishes an authenticated encrypted message on behalf of a different user, but there's no api for that... exactly the api that is being asked for in these requests to add a federation api.