892 karma · joined May 23, 2009
https://i.imgur.com/0Ar0ta5.png
My point being: there ARE other iOS versions in use. I have a backup working iPhone 4 turned on right now. It won't upgrade beyond iOS 5 (I think it's iOS 5). But somehow the author ignores all those 0.1% iOS versions, yet shows them for Android (with 4 decimals no less).
"spitzen sparken blinken lichtzen" -> "pointed sparkles flashing lights"
https://github.com/slava-vishnyakov/lapis-example
It is impressively simple to code:
https://github.com/slava-vishnyakov/lapis-example/blob/maste...
"Documentation for .... bare-metal provisioning are forthcoming."
That's kind of a downer, hoping for a sooner release.
$ ab -n 100 -c 100 http://shortfin.io/
Requests per second: 1363.85 [#/sec] (mean)
* Not sure about the index support. Didn't try.
My idea was quite simple. I have some data at work (databases up to 30GB). Sometimes we hope to find something better. The main question was - will RedShift help, will it be radically faster? Will it be radically easier?
The answer for me - no, it won't help in my case, we need that 30GB data in real time, it looks like RedShift is more when you have 1TB+ data. Yes, it is radically easier.
It seems that it actually supports it http://docs.aws.amazon.com/redshift/latest/dg/r_EXPLAIN.html
The local setup was quite usual: PostgreSQL 9.2, Mint 13, default conf in VirtualBox in iMac i5 12GB. (read: home computer, no tuning)
For me the result is that mostly RedShift is on par with local PostgreSQL, sometimes even winning for <5M rows. So with better PostgreSQL tuning you can probably stretch it, but not for as much as RedShift can do for REALLY big data.
Also the big deal was that RedShift scaled linearly.
All cryptographic operations involving symmetric or
private keys are performed on the client side
Each general filesystem node (files/folders) has an
encrypted attributes object attached to it, which
typically contains just the filename.
All symmetric cryptographic operations are based on
AES-128.
Each file and each folder node uses its own randomly
generated 128 bit key. File nodes use the same key
for the attribute block and the file data, plus a
64 bit random counter start value and a 64 bit meta
MAC to verify the file's integrity.
Each user account uses a symmetric master key to
ECB-encrypt all keys of the nodes it keeps in its own
trees. This master key is stored on MEGA's servers,
encrypted with a hash derived from the user's login
password.
In addition to the symmetric key, each user account
has a 2048 bit RSA key pair to securely receive data.
Its private component is stored encrypted with the
user's symmetric master key.
MEGA supports secure cross-account access to folders.
MEGA supports secure unauthenticated data delivery. Any
fully registered user can receive files or folders in
their inbox through their RSA public key.
(MEGA) is also our first JavaScript projecthttp://groups.inf.ed.ac.uk/links/examples/citations.links?_k...
Namely: 0. Not readable by any measure and too long 1. What's encoded there? 2. Do URLs expire? 3. Does each link require some amount of memory to save the state? 4. Is it possible to construct malicious URLs that call arbitrary function with arbitrary argument?
In Soviet Russia the Limit Camera Speeds You..
A few years ago there was an experiment in which similar camera (with speed reading) was installed on a inner circle of Moscow (called smth like "3rd transport circle"). The result? There was a huge increase in speed - people were actually COMPETING who can set a record! (Even worse - they were trying to catch a photo of the sign showing their extreme speeds). The camera was removed (as far as I know). Never seen any other cameras with actual speed indicator in Moscow ever since.
Actually there was another experiment that did work in Russia. On a highway a local group placed funeral wreaths (I'm not sure whether this is what they actually called in English) along the highway (there were no dead people, just wreaths). Net result? Everyone were driving within speed limit (which is almost unheard of in most of Russia). When pulled over drivers were asked about "why", the usual response was something like "well, it got me thinking that maybe it just isn't worth it to drive fast..."
This is a very-very weird article.
Fragmentation is all around. Yet it all works.
Somehow when it comes to Android - it's the "go to response" when something doesn't work. It makes me feel like every article that uses "android fragmentation" isn't very well thought (or maybe was even paid for Android bashing).
IMO NetFlix wrote iPhone version earlier because a year ago it seemed like iPhone is going to be the only platform worth pursuing, not because of "Android fragmentation". They just started iPhone version much earlier.