News for hackers. Stuff that matters.
Re:Kite: Thoughts on Security by Zombieball on Thursday April 21, 2016 @04:32PM (#11545134)
Expanding upon this line of thought I am not sure their comment RE: storing data indexed in 32GB of RAM holds any meaning considering it requires a hop over the wire to access. Locally stored indexes on disk would likely be much faster.

I would imagine a smooth update mechanism could allow you to update file indexes without loosing too much agility on feature development but come with huge security gains.

Re:Kite: Thoughts on Security by MichaelGG on Thursday April 21, 2016 @05:30PM (#11545482)
Well they say "machines" so it might be much more than 32GB. (Though on disk it might be strongly compressed.) And on HDDs, a few seeks is actually slower than a network round-trip.
Re:Kite: Thoughts on Security by Zombieball on Thursday April 21, 2016 @06:24PM (#11545760)
Uncompressed might indeed eat up tons of disk space.

Admittedly I was thinking of an SSD + some caching in RAM when thinking of this timing. But I was always under the impression an HDD seek would be on the order of 10's of ms? I'd assume a query to a cloud service would be on the order of 100-200ms.

Re:Kite: Thoughts on Security by MichaelGG on Friday April 22, 2016 @11:07PM (#11553956)
The network latency should be somewhere around 40ms assuming you're in the US on a proper connection. If a query takes 10 disk seeks (10ms each) vs 10 RAM accesses + HTTP parsing...