User story: As a mobile user who clicked a Tweet a Fact link, I'd like to be told that the image was shared using the Wikipedia app so that I can download it and share images myself.
The links look like this: https://en.wikipedia.org/wiki/Barack_Obama?source=app
A banner that tells mobile users that the link they clicked was shared via the app and directs them to either Google Play or iTunes Connect would be fantastic!
@Deskana: can the link be changed to a standard routed hash, e.g. https://en.wikipedia.org/wiki/Barack_Obama#/source/app ?
My main worry is cache purging: while currently non-canonical URLs are not cached, my paranoia suggests that in corner cases, such URLs might get cached and miss a purge, i.e. someone sees a vandalized page, tweets, and then people who follow the link will keep seeing the vandalized page even after it's been fixed. This can be addressed by redirecting such links to canonical locations or with internal rewrites, but such measures would be nice to discuss beforehand. It's not the first time when something gets implemented after a talk with analytics, but without considering operational consequences - can we do something to prevent this in the future?
@MaxSem the proposed change works for me, how would you recommend representing multiple parameters, in case we need them? Also, note that for the final version of these URLs, serving the cached version (by passing an explicit oldid) is a feature, not a bug: the snippet only makes sense within a specific revision (it might be gone in future versions of the article,as you observe). The vandalism use case is one that we discussed, I don't think it should be addressed by pointing users to the most recent version of the page, but it's @Deskana's call.
Regarding your second point, it's the PM's responsibility to obtain Ops sign off about the viability of Analytics recommendations. @Deskana, let me know if there's something we can do to improve the process.
Just add a "/" or some other delimiter you want, it should be possible to run a regex over it (if we use OverlayManager in MobileFrontend, it already has this feature, e.g. see the editor, the hashes are #/editor/0, #/editor/1, and so on).
I still care! But, this ship sailed a long time ago. Setting priority accordingly...