Please read my reply carefully. I was explaining that noreferrer does the same thing as noopener, but also hides the referrer. Usage of noopener it self does not hide the referrer. We have already added a parameter to disable usage of noreferrer within Parameters > Display of your web address fields.In your earlier post you've said that noreferrer hides the noopener and the referrer info, here look, its your words:
Facebook has them for me because I am using Chrome, which has security patched the issue and made noopener the default behavior. Your browser has not. This means not all the URLs for you will have noopener until Facebook finishes updating it from their end or your browser security patches it. If you're using Chrome and noopener is still missing then be sure to update your browser. Twitter has already begun rolling out this change internally and you'll see noopener in FireFox and IE. Expect more and more sites to be adding it. Waiting for browsers to fix this vulnerability is not an option as not everyone even bothers to update their browser.fb is using it carefully, why not here?: