3 ms·
Not sure if you've censored that auth token preemptively, but if not, you should consider it :)
by nexuist 5y ago
Not sure if you've censored that auth token preemptively, but if not, you should consider it :)
- 1vuio0pswjnm7 5y agoWithout logging in to Twitter, if you look at the HTTP and HTML sent from twitter.com when you make a request (I try to log all traffic to/from my computers), you will see the exact same token. There's nothing "secret" about this header. Thus, there's nothing to censor. I have seen it in other people's code as well. It gets sent to everyone who visits twitter.com.
- nexuist 5y agoAh okay. Weird design choice since it doesn't seem to be authenticating anything, but glad that you thought about it!