# http -> https has caused issues with a specific challenge

Take a look at this challenge: Print This Question ↓

It asks to print the exact contents of the question. Cool, right? There's even a comment by ETH saying "Let this be a reminder not to edit this post. Ever. Or we're all screwed."

However, Community edited the http link in there to become https. This is necessary for the https transition; however, it makes it look like all of the answers are invalidated (see below). Should this be kept this way or rolled back?

Note that the challenge's specifications point to a specific revision, which means that the answers appear invalid but if you look carefully are actually good according to the original specs.

Also note that none of the answers have been active for less than half a year and...

wait Mr. Xcoder just rolled back the Community edits.

So as a general question, should the https revisions be kept (invalidating some answers) or rolled back (potentially causing link rot) for really old challenges?

• Note that the same type of thing invalidated bots in Helka Homba's Red vs Blue Aug 10, 2017 at 23:08
• In addition to invalidating current answers, it also means any new answers will be effectively performing a new, slightly different task. Perhaps the original text should be added as a code block? Aug 10, 2017 at 23:10
• @trichoplax it's already in a pastebin link in the original, so it's not too much of a problem. Aug 10, 2017 at 23:10
• Ah I see - that link goes to the source of the specific revision, not the source of the latest version. That's very handy. Aug 10, 2017 at 23:13

# Roll back

The https transition made by Community is, in this case, an edit you would reject as a suggested edit in review, since it drastically changes the meaning of the post, telling people to print something different than intended.

• ...made by Community is, in this case, an edit you would reject... Community is hurting the community. fire-community ;) Aug 12, 2017 at 2:06
• @totallyhuman but you can't really reject it since that user has diamond Aug 12, 2017 at 11:27
• +1 SE has http->https redirection anyway. The only reason Community made the change was likely to save everyone a redirect (or maybe some weird part of the transition).
– Poke
Aug 15, 2017 at 13:44
• @Poke The redirection didn't always exist... Aug 15, 2017 at 13:45
• At the time of this metapost it sure did. That fits into the "weird part of the transition" bit of my comment
– Poke
Aug 15, 2017 at 13:47
• @Poke The edit by Community was made on 2017-04-13 12:39:07Z. I'm pretty sure it didn't exist back then. Aug 15, 2017 at 13:48
• I didn't argue that it didn't ever exist
– Poke
Aug 15, 2017 at 13:51