What’s the best way to deal with the last point, though? Flushing all the cache on network changes doesn’t sound that bad an idea.
-
-
Captive portal detection probably should be in a separate tool, e.g. HTTP 204 method, maybe with notifications via DBus?
-
How does Chrome on Android (or ChromeOS) deal with captive portals? Doesn't Chrome have its own DNS cache?
End of conversation
New conversation -
-
-
something like (network change) -> enter learning state and probe -> (probe resolvable) -> enter normal mode
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.