timemachine

Rows in the database are never updated or deleted. Only new rows are added.

John Lee is one of my favorite narrators and his reading of the Count of Monte Cristo is wonderful (even at 47 hours).

Ron Chernow’s biographies of Grant, Hamilton, and Washington.

Candice Millard‘s “Hero’s of the Empire” (about Winston Churchill) and “River of Doubt” (Theodore Roosevelt) are both interesting looks at important historical figures in situations we don’t often prescribe to them. Her first book “Destiny of the Republic” (James Garfield) is also good but the other two are superior.

“David and Goliath” by Malcolm Gladwell.

A fun read and primer on the subject. However, I would like to see more emphasis on including a time stamp as part of the signed payload. The reason is multifold: (a) Most importantly prevents ‘replay attacks’ [1]. Systems that need to send send the same command will do so with a unique time stamp and, therefore, a unique signature. (b) The time stamp + signature is an idempotency key. Your key cache’s TTL is the same as the timeout for your time stamp rejections. (c) To a lesser extent bolsters the system against a brute force length extension attack (see the Flickr API flaw in the reading) by reducing the time the middle-man has to correctly calculate the glue bytes.

1: https://en.wikipedia.org/wiki/Replay_attack

Came to make the same comment.

FaceBucks

I’m interested in background as to why, specifically, government-backed attacks are reported differently. In my experience who funds the attack is anecdotal to the triage, midigation, and reporting of an attack; be it from government, corporate espionage, or an independent group.

Hi. This is Dan, CTO of Meter Feeder (YC W16). Nice experiment. For comparison, Jim (my co-founder) and I built the MVP of Meter Feeder in a weekend back in Oct '14.

We spent a lot of time working on the business requirements that we got from our first potential customer.

I'm not a lawyer; this is not legal advise.

This is one of those questions that have 100 different answers. The first place to look for the answer is in the employment agreement the employee signed (if there is one). Also review the employee handbook for any notes.

Next look at how the IP was developed. Did the employee use any hardware, software, or anything else owned by company while developing IP? This includes any existing IP owned by the company that the employee may have built on. Write software on the boss's computer or on the boss's time then it belongs to the boss.

Next, did employee discuss IP with any coworkers on company time? This is usually not a big deal in the real world but something avoid if at all possible.

If you have those bases covered then contact an IP lawyer and get get a provisional patent. The lawyer will also review anything that is important for your jurisdiction.

Good luck.

Thanks for sharing. Kube is a direction we want to go with our servers and this looks to reduce the barrier to entry.

We work with them to set up the initial zones (GIS coordinates are easy to find online). And there is an administrative dashboard that we provide the municipal director of parking where they can adjust the rates. It usually takes about 10 minutes for one of our team members to set up a new city.

Hi. I agree! Parking is a hassle everywhere, even in the US. Meter Feeder is working to challenge the pain points of parking and create a new and better way.

One of the goals of our system has always been to augment existing systems instead of replacing them.

- Dan, Meter Feeder CTO

WebRTC is a great tool and I expect to see more examples like this that will drive how we think about collaborative business tools over the next 5 years.

I love this article. Excellent analysis and insight.

It also references one of my favorite xkcd comics.

The irony that this article, about how RuneScape is an anachronism of the mid 2000's, is hosted on digg.com is not lost on me.