491 karma · joined October 10, 2014
Also when it comes to self-defense laws, most states require the shooter to genuinely believe he/she is in mortal danger before shooting. Sure some states have stand your ground laws that allow more, but I would not say it's so clear-cut that people can just start shooting other people or property when they believe their rights are being violated.
It's not the people's decision as to whether a drone is violating the law. If you were arguing having the government have that right or responsibility that's a lot different. But even so shooting down aircraft is not something that should be done likely. There's a reason the FAA makes it completely illegal. Shooting a drone for flying over your property could make it go out of control and injure others.
Obviously their onboarding process is terrible, but putting new users aside, the app works pretty fine for existing customers. It gives you your boarding I passes, flight status, and reservations automatically. You change seats and check your upgrade status. I've even booked fligjts via the mobile app before (I've never seen that "something has gone wrong" dialogue at the end).
Overall I've found it functional, which I cannot say for many other apps made by large companies (I'm looking at you Chase).
And I wouldn't go so far as to say the lack of great user onboarding experience represents some sort of culture problem. Maybe they just don't have a large team? Maybe their engineers don't have UX experience? Maybe they haven't done user onboarding studies and realized these problems? (Personally I think it's lack of staffing, but I don't actually know anybody who works on the app.)
There are some use cases this does not cover, such as authentication across multiple systems, where one or more may not have access to the authentication source, but even in that case it'd be preferable to have a separate, internal, private microservice that exchanges tokens for session information.
None of this will stop an attacker that has network access, but that's not what the article is considering, and if somebody is inside your network you might have bigger problems than session hijacking.
But seriously, I was expecting some actual discussion about how GPG still isn't easy (or possible for that matter) in modern webmail clients, or even something relating to the usability of common GPG GUIs, but instead just got a guy complaining about how he was pressing enter too fast and missed a dialog box, among other nonsense complaints.
Personally, the GPG CLI acts exactly as I expect it to, being a CLI and all, and I don't expect non-advanced users to use it.