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
{{ message }}
This repository has been archived by the owner on Sep 13, 2019. It is now read-only.
with http-remixing now working properly (giving the user an http link for their remix, which will also work but look horrible if accessed via https), let's figure out the best way to expose the teaching/learning moment when people visit their remix of an http original source.
We can update the top bar to now say something like "The web is moving to https, have a look at what your remix looks like via https, by the way it'll look all kinds of wrong, because of mixed content, ask your treacher/click here to learn about that", with the bar giving a link to the https page if you're on http, and a link to http if you're on the corresponding https page.
The text was updated successfully, but these errors were encountered:
I am landding #295 in the interrim, which just adds a note that there is an https link too that people can click on, so that we can blog about the fact that we finally support http now.
And then we can iterate on the specifics in terms of the copy and styling with that in.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
with http-remixing now working properly (giving the user an
http
link for their remix, which will also work but look horrible if accessed viahttps
), let's figure out the best way to expose the teaching/learning moment when people visit their remix of an http original source.We can update the top bar to now say something like "The web is moving to https, have a look at what your remix looks like via https, by the way it'll look all kinds of wrong, because of mixed content, ask your treacher/click here to learn about that", with the bar giving a link to the https page if you're on http, and a link to http if you're on the corresponding https page.
The text was updated successfully, but these errors were encountered: