OTPs is not going to prevent governments, internet service providers, cafe owners etc from being able to intercept traffic and determine exactly what a user is posting. Which is not something anyone should want from a social network.
OTPs is not going to prevent governments, internet service providers, cafe owners etc from being able to intercept traffic and determine exactly what a user is posting. Which is not something anyone should want from a social network.
With OTP you can easily encrypt your data so nobody can read it inflight over HTTP.
I guess you need to have the creativity to extend the link knowledge with encrypting the data with the OTP.
Certificates are a scam.
My solution which is convoluted and relatively insecure if you have a persistent MITM is to require a password change that you can encrypt with the old password, then the MITM has to remember the old password to know the secret.
But you are right that OTP only are safe after the secret has been shared. Just like all crypto including HTTPS and SSH.
HTTPS is _not_ more secure in any way. The lock icon is an illusion.
As for the technical reasons:
- Big-ints are not trivial in js.
- DNS is centralized.
OTP is about authenticating clients, using a preshared secret established by unspecified means.
They’re completely different things. It’s like you’re comparing Apple (the company) and Orange (the city in NSW, Australia).
Cleartext HTTP is bad for various reasons, one of which is that pervasive monitoring is an attack: https://www.rfc-editor.org/rfc/rfc7258.html.