You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instagram recently introduced a feature when someone shares anything on the app, an igsh parameter gets appended as an identification who and to whom the content was shared.
The app even shows the account of the sendee.
If this igsh link is removed when sharing, then it won't be recorded by telemetry.
Motivation
This would again, anonymize sharing and not leak account accidentally and the user won't have to manually always delete the igsh link whilst sharing content among his peers. This way also Meta can't map your contacts or skew your algorithm based on what you are likely to share among them.
Its a simple privacy feature where the user won't have to always manually delete the igsh part of the link every time he shares something.
Acknowledgements
I have checked all open and closed feature requests and this is not a duplicate
I have chosen an appropriate title.
All requested information has been provided properly.
The text was updated successfully, but these errors were encountered:
Feature description
Instagram recently introduced a feature when someone shares anything on the app, an igsh parameter gets appended as an identification who and to whom the content was shared.
The app even shows the account of the sendee.
If this igsh link is removed when sharing, then it won't be recorded by telemetry.
Motivation
This would again, anonymize sharing and not leak account accidentally and the user won't have to manually always delete the igsh link whilst sharing content among his peers. This way also Meta can't map your contacts or skew your algorithm based on what you are likely to share among them.
Its a simple privacy feature where the user won't have to always manually delete the igsh part of the link every time he shares something.
Acknowledgements
The text was updated successfully, but these errors were encountered: