> The federal body said work it was doing to revise and update information about where the historic quake struck had caused computer systems to misinterpret the data and think it was seeing a novel event.
It doesn't seem that implausible for a program to be reading through a dataset and issue a notice for a measurement above some value. If the dataset encoded years in just two digits, it (almost) makes sense that the program would report it 100 years off.
Imagine:
with open(file) as f:
for record in f:
year, month, day, time, magnitude = record.split()
if magnitude > 5:
raise_alarm()
On iOS, I've used Pocket Earth for years and really like it. They added topographic maps awhile back, and also have integrations with Wikipedia/Wikivoyage. I have pins and stars of POIs from all my trips saved (and exported) through that app.
Definitely going to be looking more into this. I am just about to start a project that needs ACLs, and I was surprised to find that I was going to have to write a solution myself.
In case I just missed them, are there some comparable projects to this? Is there an established library in the space?
I have been there many many times. This is the reason for writing that library, because there are no good solutions that cover 99% of your cases. RBAC is limited, ACL is a managing nightmare, DAC is also limited, and so on. What really hit me where those AWS IAM policies which are plain beautiful, hence this library.
However, usually major programming languages have some sort of ACL/RBAC module around.
I use a much smaller solution than this which just registers a list of permissions in memory of the form: role x can perform action y on resource z and then offers checks like can.Manage(resource,role). So it avoids the policy docs and just does registration in code, and is a bit simpler. This library offers a lot more obviously, and solves a broader set of access problems, but depending on your needs the solution can be really simple and you might be better to write it yourself in one file and avoid another dependency.
That's more or less the situation I'm in, but with multiple applications. The idea is to pull out the "identity x permission x resource" logic so that each new project doesn't need to re-implement it..
Oh yes, I'm using a pkg shared between apps, didn't mean you should rewrite it each time, just that it can be much simpler than the linked pkg. Not aware of any widely used ones, you should release yours at some point if you extract it. The one I'm using is here in case it is of interest: https://github.com/fragmenta/auth/tree/master/can
I'm not too familiar with how heavily locked down iOS is: does this "WebView only" policy only apply to apps released via the AppStore? Meaning, can I build locally and sideload install an app that uses my own engine? And if that existed, could I open source it for others to use?
These days you can sideload apps with a free developer account (with certain restrictions), but it's meant for development - AFAIK using it as a general-purpose app distribution mechanism is a violation of Apple's ToS. But people do it anyway, and you could too.
Separately from the ban on third-party browsing engines, iOS has technical restrictions preventing you from mapping unsigned code as executable, so JITs don't work. There may be some ways around that if you have a developer signature, but its messy at minimum.
This reminds me of the 7 Up Series (https://en.wikipedia.org/wiki/Up_Series), where the same people are interviewed every 7 years, starting about age 7. The director of that series is unfortunately quite heavyhanded in the questions he asks, but the project itself is quite interesting. Next episode will show in 2019, I believe.
Yes, but if you're trying to get around the duplicate detector, you can usually just append a query string like '?2'. Or, if the server tries to interpret query strings and that would be bad, it'd be friendlier to the read to instead use a non-existent div like '#2'. Bypasses the duplicate detector, specifies how many resubmissions, and doesn't jump the reader somewhere in the article. (Although I should note that I think the one OP chose is one of the two best ones, so no real harm done.)
It would be cool if there were more talk about properties we have observed of these configurations/which are more probable at any given instance, and efficient ways of computing such.
