How long until a canvas is used to render the full chrome of a web browser (e.g. including the TLS padlock), showing a fake benign URL in the (fake) address bar while having the user interact with a malicious page?
Yes, but this "emergency" UI of the OS could be improved I think. (Also that functionality could have been build easily with normal DOM and JS, cancel and override all events, etc)
> we include it in our terms and condition and privacy page, but I don't think users truly grasp how those tools work
Since you did collect the metrics, you had direct knowledge of how many users opened the T&C and scrolled down to the place where you mention you're recording their session.
Would be interesting if you can share an aggregate statistic of that.
All the questions about sneeze are either about open air, or Newton's third law. Did really no one ask what happens if you sneeze while wearing a spacesuit helmet? Does the visor have a windshield wiper on the inside?
I'll ask the obvious: wouldn't the aircraft just take to the skies directly, without bothering with the formality of setting their transponder, if they were knowingly escaping an apocalypse scenario?
There’s no formality. For planes with ADS-B out, it’s on when the plane is on (barring it being explicitly disabled by yanking the fuse).
Plus transponders are really convenient when you’re trying not to crash into other air traffic. Particularly in a scenario where you might be expecting ATC to be unavailable or abandoning their posts.
AFAIK the transponder kind of turns itself on when powering on the plane, you'd have to explicitly disable it but then you'd have weird discussions with the airport tower guiding you to a free timeslot on the runway which would just delay your takeoff, since ignoring the airport tower is a good way to not get off the ground at all because you'll accidentally be hit by some other plane.
In a theoretical scenario of the billionaire class of the world having some kind of "advance warning" of the apocalypse, they'd be taking to the air in the hours or several days prior to a total disaster happening. Meaning this would be done while the local governments were ostensibly still functioning, in which case you can't just have your private jet depart without active ADS-B and in-the-clear voice traffic for ground, and air traffic control coordination.
If governments and airspace control have already collapsed, post tense, then of course anything goes.
Colliding with other planes is going to impede your escape plan, so it would still be a good idea to turn the thing on. No further action needs to be taken for the ADS-B output to be correct, it works once it's powered on.
They wouldn't have to set anything. The transponder on almost any modern plane defaults to automatically on, either immediately or at takeoff. With Mode C (reporting altitude) or S (& reporting more) and squawking 1200 (VFR).
This drives me up a wall. Short of UX and front end devs taking this seriously, ive always wondered if theres a way for an OS level / browser level UX library to keep track of the "clickable state" 20ms ago (configurable to the user's reaction time liking) so the thing I click on is what my brain thought it was clicking on.
The better solution is developers and designers taking a sense of pride and craftmanship in this sort of thing. So many of my least favorite interfaces are presumably designed and implemented in an environment with a gigabit connection to their apps backend so they never catch it.
This one has somehow found its way into the iOS photos app of all places. Something is deeply amiss in the industry if the corporate avatar of design misses that one.
I sometimes use a trackball — without a "scroll wheel".
So in Google Maps on the web, I'd have to click the + and - buttons on the screen repeatedly to zoom in and out.
But those buttons don't always stay put. There is a status bar underneath it, that sometimes contains text so long that it wraps: and then that pushes the buttons up.
This. I'm not a fan of expanding links, like when a user hovers over a small button with an icon, and it expands to reveal the full button name, but the content around it (like other buttons) shift because of the size change.
It's a bit ironic the laws of UX is presented this way with gaudy graphics that are cumbersome to scroll through. They take up a lot of screen real estate and would disrupt what the typical user is used to.
reply