Possibly a browser cache issue, at least with regards to @Analogman's problem. Not sure if it explains @uncool2pillow 's problem, but it's the only thing I can think of at present. We applied a major software update to the board last night, so some browsers/devices are probably getting confused because of leftover cached data from the old board. For anyone else who runs into this issue, try clearing your cache/browser data first (on Chrome, this would be: 3-dot menu -> History -> History -> Clear Browsing Data).
Any other issues (or suggestions, or complaints), please send us a P
