Wikipedia talk:Wikipedia Signpost/2011-11-07/Technology report


 * So does this mean the various issues with https support are being dealt with? Also, it would be convenient if https links to wikimedia pages (e.g., for a link to a specific article revision) within edits would automatically be translated back into ordinary http links, so other users get whatever they prefer (http or https). Edit: Oh, I see, https can be used for the same URL paths that http uses now – this should have been mentioned in the article. Nageh (talk) 17:18, 11 November 2011 (UTC)
 * Yes, you can just change http to https in the URL now, a fact only dropped from this article on the grounds it has appeared on all previous occasions the switchover has been mentioned. As you say, though, they is no automated switching based on user preference at the moment - so someone else can still link you to the "wrong" version. - Jarry1250 [Weasel? Discuss.] 17:48, 11 November 2011 (UTC)
 * Right, but it's actually already possible to use protocol-relative URLs in wikitext, which provide automatic switching, i.e. will point to HTTPS or HTTP depending on what the reader is using:
 * [//en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2011-11-07/Technology_report] (results in [//en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2011-11-07/Technology_report])
 * Regards, HaeB (talk) 18:19, 11 November 2011 (UTC)

An email petitioner asked if we could change Signpost links to https; I wasn't sure if this would mess things up for people being logged-out etc. Would it be possible to accommodate both constituencies? Skomorokh  18:32, 11 November 2011 (UTC)
 * You mean the links in the mailing list email we send out? - Jarry1250 [Weasel? Discuss.] 23:40, 11 November 2011 (UTC)
 * Yup (blog, twitter etc. too I suppose).  Skomorokh   13:47, 12 November 2011 (UTC)
 * Well, the problem there is that we need a defined entry point. "//" just means "stay on the same protocol as you were before" which isn't great when you're linking from offsite (and most browsers won't even observe it cross-domain anyhow). (Plus a // link isn't recognised as a link by lots of email clients.) - Jarry1250 [Weasel? Discuss.] 17:35, 13 November 2011 (UTC)