Continuing the discussion from Moving t.co to HTTPS only for new links:
This is an outstanding move, and thank you very much for making it. This is the sort of precedent that will help others make the same move.
Some questions about next steps:
- You estimate a 10% reduction in referrer traffic for linked-to sites. Will you post some data of what the reductions actually turn out to be afterwards?
- Will Twitter institute 301 redirects to HTTPS for all past/present/future HTTP t.co links?
- And/or, will Twitter add an HSTS policy for t.co that ensures HSTS-supporting browsers will upgrade old HTTP links without needing to make an insecure connection at all? (And if so, will Twitter implement HSTS preloading for t.co?)
Thank you very much again for being a leader on this, and for leaning on Referrer Policy!