The article is a little difficult to read so perhaps I missed this.
Surely a key determinant in making your project closed source is your willingness to cut yourself off from dependencies with strong copyleft licences? And, correct me if I'm wrong, this is true at whatever depth of dependency the copyleft licensed dependency is found, which in some environments ("hello npm registry") is going to exclude an awful lot of code.
The book that I looked at had the same blurb on odd-lots-books.netlify.app as was used in my local library catalogue, so I assume it's the standard publisher's blurb?
What are these checks and scrutiny and how are they applied in the time available? Given the time available is not great ("I'm on the next flight") and the amount of money is modest if humans are involved I'm intrigued to know what could be done that $45 would cover.
It's a database lookup that takes 5-15 minutes once you get to an available officer, but then depending on what it returns you may need additional screening, which will also need to wait for someone available.
That's why if you don't have an ID, you should get to the airport at least an hour earlier than otherwise (already accounting for long security lines), and more during peak travel times. If you get slowed down, you're going to miss your flight. They're not going to speed it up for you.
To me this makes no sense at all. The visual (or computational) ID check takes a second. Why is a manual entry of someone's name/DOB something that takes 5-15 minutes? This is a process control issue, not a technical problem.
You're misunderstanding. What's preventing me from finding someone on Facebook who looks kind of similar to me, finding out their address and phone number, and then claiming I'm them but forgot my ID? Or if I'm a serious criminal planning ahead, applying for a legitimate driver's license in that other person's name with easily-forgeable documentation that less strict DMV's accept when they aren't RealID?
That's what they're guarding against. There's is no secure enough visual or computational ID check that takes a second when you're not already carrying a RealID or passport, that's the point. They have to start getting a bunch of information from databases, determining if it seems like a real person, and quizzing you on information you should know if you're the real you, and seeing if it all adds up or not.
How about we restrict airport and aircraft access based on individual's ability to do harm, rather than on the information in some trusted database? It sure seems like the major incidents in my lifetime would have been better prevented by keeping people with guns and bombs out than people with poor paperwork skills…
If you are able to follow simple written instructions and enter several pieces of information on a keyboard in less than five minutes... why would you work for the TSA?
This happened to me once, they just brought out someone (supervisor?) who asked questions about what addresses I've lived at, other similar questions I'd probably only know the answer to.
It does take longer than regular screening (most of the time was just spent waiting for the supervisor -- I'm not sure they were spending time collecting some data first), if that causes you to miss your flight you miss your flight.
It seems plausible to me that $45 could be about a TSA employee's wage times how much longer this takes. In aggregate, this (in theory) lets them hire additional staff to make sure normal screening doesn't take longer due to existing staff being tied up in extra verifications.
Data brokers already know everything about every American so the TSA is just buying existing information from them. Then they can quickly quiz you on the information to verify that you are you. https://network.id.me/article/what-is-knowledge-based-verifi...
My view may be as realistic as these architectural drawings but I've long thought that some sort of micro payment system would address a lot of problems, many more significant than tipping software developers.
The problem isn't "to date" the problem is what might be.
Sure, maybe the CloudFlare CEO seems like they "do the right thing" and then the administration gets pissed off at something CF related, they lean on the CF board and you've got a new CEO and maybe CF is sold off to "a friend of the show".
Nothing specific to CF here it's just how all US companies need to be viewed.
I too use pipenv unless there's a reason not to. I hope people use whatever works best for them.
I feel that sometimes there's a desire on the part of those who use tool X that everyone should use tool X. For some types of technology (car seat belts, antibiotics...) that might be reasonable but otherwise it seems more like a desire for validation of the advocate's own choice.
FWIW the "industry sources say" line on the incident is that it occurred on 30 October[1], so further back than ten days ago but of course there may have been other CME incidents at that time.
The European Agency Aviation Safety Agency [2] instruction describes the characteristics of the incident but not the date.
I don't have ADHD but I would find that useful (I'm not a mac user so your implementation is not for me).
I have used pomodoro timers that have a sound (for instance a clock ticking) and that's a useful way to be reminded. Unfortunately the ones I've seen to date have a reasonably limited range of sound configuration options, generally a one second tick. I would prefer to hear a quiet sound every thirty seconds, I'd also be interested in the option of a voice announcing, say, every five minutes elapsed.
> I think with these kinds of ideological issues, all one can do is vote with their wallet
Needs to be viewed in the light of the distinctly un-open market in which airlines operate. There are only so many airports, and only so many slots. I might wish to start another airline which customers may use an open solution but the reality is that incumbents have a massive moat around them. No market, that I know of, is perfect but air travel is an unusually distorted one.
This was going to be my comment. "vote with your wallet" only works in open competitive markets. But (with a few exceptions), this is not the world we live in. Regulation is the only option left. You have to vote with your vote to get laws in place that force industry to behave better.
Though much less distorted in the EU than in the US. It's common to have the choice between 2-3 different airlines to get from one place to another, and if that's not good enough the next major airport is frequently just a 2-3 hour train journey away
Surely a key determinant in making your project closed source is your willingness to cut yourself off from dependencies with strong copyleft licences? And, correct me if I'm wrong, this is true at whatever depth of dependency the copyleft licensed dependency is found, which in some environments ("hello npm registry") is going to exclude an awful lot of code.
reply