Offline mode doesn't work for visitors on plain HTTP. Browsers allow service workers only on secure origins, so an HTTP visitor misses offline mode and anything else built on it.
The idea: detect whether a client can use HTTPS, and if it can, gently suggest switching. Rules for how:
Never force it. HTTP stays a working, supported choice (old devices, odd networks, people who simply prefer it).
Don't be annoying. No popup or interstitial, and no asking again on every page.
Give a reason, which is that HTTPS turns on offline mode and other features. Offer the link and let the person decide.
This needs some discussion on how to do it tactfully before anyone builds it. Open questions:
How do we detect that HTTPS works for this client? For example, a small background fetch to the HTTPS origin, with the suggestion shown only if it succeeds.
Where does the suggestion go: the offline banner, the menubar, a line on the offline page, or near the compose box?
How is a dismissal remembered, and for how long?
Should the suggestion stay quiet until the person actually tries something that needs HTTPS, such as going offline?
Planned as its own Railspike cycle: https_nudge. Related: the offline compose item, and the request for a non-technical version of https://zenmemes.com/offline/ at the top of that page.