I trust it but there is a major misunderstanding of end to end encryption. Some implementations the platform holder does not have a key to decrypt data but it is far from a requirement. All end to end means is there’s a blocker preventing the network from seeing what you send not twitter who im assuming has a copy of the key.
It’s like ssl but done at the application layer. Nobody in the middle can read it except it’s nobody in the middle of you and twitter and twitter and the recipient. If you put something on a platform and they have the key they will always be able to read it if they want to.
are you being dense on purpose? sender and recipient are both users. never twitter.
i’m not saying that twitter’s messaging is secure. the opposite. what i’m saying is that you statement of “All end to end means is there’s a blocker preventing the network from seeing what you send not twitter” is 100% objectively wrong.
I trust it but there is a major misunderstanding of end to end encryption. Some implementations the platform holder does not have a key to decrypt data but it is far from a requirement. All end to end means is there’s a blocker preventing the network from seeing what you send not twitter who im assuming has a copy of the key.
That is NOT end to end encryption. That is transport layer encryption. So basically SSL
End to end is from sender to recipient. No one in the middle should be able to read anything
It’s like ssl but done at the application layer. Nobody in the middle can read it except it’s nobody in the middle of you and twitter and twitter and the recipient. If you put something on a platform and they have the key they will always be able to read it if they want to.
are you being dense on purpose? sender and recipient are both users. never twitter.
i’m not saying that twitter’s messaging is secure. the opposite. what i’m saying is that you statement of “All end to end means is there’s a blocker preventing the network from seeing what you send not twitter” is 100% objectively wrong.