Hacker Newsnew | past | comments | ask | show | jobs | submit | billjive's commentslogin

I'm from Iowa City! It's awesome to see this pop up on HN. IC has a number of great older bars like this. Sadly my favorite (The Sanctuary) closed recently and may be lost forever.


As it happens, I'm looking at a travel guide to include Iowa City. I had the "Hamburg Inn No. 2" as a food-stop and "Devonian Fossil Gorge" as a tourist-stop.

Am I missing something? (I'll probably head out there for research in May, ha ha.)


Iowa City natives raise up! There has got to be less then a dozen of us (on Hacker News)!


Any City High grads here? The School That Leads... :)


I was from that area as a kid, West Liberty. Been awhile since I've been back up there.


This specific quote from the article made me think of lawmaking - the more detailed the law the harder it is to pass (someone can always fine something to nitpick). Therefore, laws are best at establishing goals, principles, guide rails, etc. Nothing is perfect but the way in which laws are implemented SHOULD remain a separate part of the law passage.

Separate rant: I live on the west coast and am annoyed when I vote because of the number of ballot measures. None of them are sufficiently detailed and fall victim to vague language that's open to interpretation. I'd rather "hire" law makers to do the hard work of details law creation.


Nah. There's no valid reason for lawmakers to delegate so much authority to bureaucrats. We should eviscerate the administrative state and if legislators want to prohibit something then they ought to specifically write it down. If that means it becomes harder and slower to pass new laws then that's fine. It should be a careful and deliberative process.


Some of that vagueness is intentional and not always for nefarious reasons either. When getting my the FCRA cert, there definitely a few requirements that were obviously very open ended so the gov could either pursue a potential unforeseen circumstance or not stifle business. The vagaries in laws has always been interesting to me. Unfortunately, I don't remember any definitive examples since I took the test years ago now.


That is right, and further - I think about IRBs like I do non-profit boards. One of the key tasks of a board is to determine what risk the organization is willing to bear. I think the IRBs at these institutions are 1) following federal laws but 2) making a judgement on the risk the institution is willing to sign up for. For example, for many clinical trials are distributed to multiple "sites" where the trial is actually administered. Many of these sites are universities. What the University of Iowa is willing to bear is different than the University of Michigan and the IRBs reflect that.


There are different IRBs to review animal research[1]. I believe it created for an ethical framework around the use of animals in science. Same thing: what are "we" accepting of when it comes to research of this nature?

[1] example: https://animalcare.umich.edu/institutional-animal-care-use-c...


Jim and I were on my company's board (Jive) and he absolutely has a technical background.


I would highly recommend "Hellhound on His Trail." Both a good look at King and the hunt for the assassain: https://www.amazon.com/Hellhound-His-Trail-Electrifying-Amer...


The problem with this statement is that Amazon is largely matching firebase functionality. They just announced streaming JSON out of dynamodb, and the new lambda functionality means you can trigger events on changes and push out updates. It wasn't explicitly stated but I viewed this as a firebase competitor.


How did Amazon detect your key in the wild? Or did they notice based on usage patterns/activity in your instances?


All AWS keys I've seen start with 'AKIA'. I am assuming that they have bots that search Github and other search engines for access keys. At that point it is easy for them to tie them back to an account and notify the user.


They must only have started doing that recently. This project has been out in the wild for at least a year.


Well, kudos to them for doing that, at least. Of course it's awful that you could be out ~$3k, but imagine how bad it could have been if they hadn't been so proactive.


Yeah, it would have been another day at least before I checked amazon again.


Luke, drop me a note at werner [at] amazon with a link to the support ticket you created, and we'll see what we can do.


Wow, talk about customer service!


horray AWS!


Ha - no --- they do that when they see a spike in charges.

Or maybe it's just a coincidence they emailed immediately AFTER he racked up +3000$ in charges.


Email linked to my GitHub profile, so I would say by searching. But that's an assumption.


I bet you 20 bucks they searched for your key after they investigated the sudden spike in your charges :D


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: