Isn't the iPhone basically what the Newton was supposed to be, but with a soft-keyboard rather than text recognition (which could be added to 2.0 easily enough)?
(which I can, BTW, I stole my dad's many years ago, but I think it got lost in a random move), do you know WHY a slide rule works, and how to make a slide rule for addition and subtraction...
Thats what the Bloom filter suggestion was, but the bloom filter is better because its a small amount of data you store locally, and then only do you send a query to google.
The GPLv3 is full of FUD, a lot of it well founded. There is a reason I won't use it, but then even GPLv2 isn't as free as I like (BSD forever, yada yada yada)
This article is also FUD, and unlike other GPLv3 fun, it is NOT well founded.
That 6% are actually using GPLv3 already is not an indication of failure, but a pretty big success, and suprisingly high. That 40% will never touch GPLv3 is not suprising, because how many of them are BSD zealots rather than GPL zealots anyway.
Because privacy preserving database queries are different, and allow you to query the database WITHOUT the database owner able to extract information, and it is true "Deep crypto voodoo"
A "blacklist" of phishing sites needs to be stored somewhere, and you need to be able to do queries against it.
It changes too fast, and is too large, for it to be stored locally.
So SOMEBODY needs to provide a database interface to it, and unless you are willing to tolerate the voodoo cryptography and serious performance penalty to do privacy-preserving searches, how else is this supposed to be done?
So what does it send, according to the FA: The blog's URL A list of all plugins and versions A list of the $_SERVER env variables
How is this information not necessary for a robust autoupdating/autonotifying infrastructure? Since the plugns are the source of so many vulnerabilities, you need to know their versions etc.
Since so much incompatibility may be caused by funky $_SERVER variables, you need to know their contents.
And the blog URL tells you who it is.
Windows Update has to send far MORE intrusive information.
There are two reasons I didn't get an IPhone a couple days ago:
The first is "all need landscape entry", as mentioned in the article.
The second is "WiFi Only mode": When out of AT&T, I don't want it to transmit data over the cell network, only on the WiFi. There is "airplane mode" (no net) and "no wifi mode", but there is no "no cell" mode that I was able to find in 15 minutes of trying with a demo unit.
Yeah, the v3 Nano is cheaper to build. Its also cheaper to buy, with a 4 GB unit now $150 and $200 for the 8 GB, as opposed to 2 GB for $150, 4 GB for $200, and 8 GB for $250.
Not having the "Where you shoot is the middle of the screen" really ups the immersion factor. For enemies in view, the WiiMote is a VERY fast way to shoot them.
For strafing, the WiiMote/nunchuck controls are also really good, because the joystick is strafe not look. Likewies, the target-lock semantics (circle-strafe mode) work well.
So in many ways it is exactly like keyboard/mouse: look with the quick device (mouse/wiimote), and strafe/move with the keys.
I think the lesson of both the Wii and the DS is that for a lot of people, notably the non-gamers, FUN is what counts.
Technology, the PSP trashes the DS. The XBox360 makes the Wii look like a joke graphically and computationally.
But the new interfaces (touch screen, WiiMote) have lead to entirely new classes of games, and new ways of doing traditional games.
EG, after playing Metroid for a few hours, I can't see how anyone could go back to the classic FPS controls, especially on a console. On a DS, the touchscreen allows very rich UIs, which are not possible with just the D-pad and buttons.
That is the lesson from Nintendo: Fun Must Come First.
I was visiting an academic CS research group, which is doing some networking protocol work they want widely adopted (eg, in Windows would be a good start).
Their release of the prototype code was "whatever", so they did it under GPL (well, dual liscence, GPL for everyone, and a free liscence for funders). They were kind of shocked when the link on their web page was now pointing to a GPLv3 description, and I explained the implications.
For FreeBSD, the kernel is BSD liscenced but pretty much all the tools are a mix of BSD and GNU v2 or later (and all from the FSF are GPLv3 soon), which is "hello GPLv3" for a lot of what you care about.
For Linux, the kernel is GPLv2 only but pretty much all the tools are the same mix of BSD and GNU v2 or later (and all from the FSF are GPLv3 soon), which is "hello GPLv3" for a lot of what you care about.
Thus there is no way GPLv3 will drive people from Linux to BSD for business use, as it really is the same impact for both.
A couple of other posters mentioned the state storing across power cycles. Being too lazy to read the paper in enough detail to create a slashdot question:
This shouldn't affect the fingerprinting, because you fingerprint on the highly-biased cells.
But how does this biasing effect interact with the true RNG operation? Have you done retention time experiments?
also, DRAM is worse on the retension time, but is it perhaps still suitable for the fingerprinting? Have you evaluated this yet?
a: Many of the bits are sorta random, but physically random. So very biased coins, but true randomness.
b: With the right reduction function, you can turn a LOT (eg, 512 Kb) of cruddy random data to a small amount (128b-512b) of very high quality, well distributed random.
And the fingerprinting relies on the fact that:
a: Many other of the bits are physically random, but VERY VERY biased. So map where those are and record them and it is a very good fingerprint. And since it is all silicon process randomness going into that, it is pretty much a physically unclonable function.
Of course, the results will be edited to show that the 2,000,000th article is on Steven Colber's continuing humanitarian work to deal with the perpetual threat of BEARS!
As a gamer who plays, I'm currently enjoying Metroid on a Wii..
When I finally get an HDTV, My $$$ are going to the evil Borg empire (rather than the Evil sony empire) and getting an XBox 360 for Halo and GTA IV.
So why should anyone care about the PS3? The zealots who got them got them already, and all the rest are just not gonna care, get a Wii (gameplay) or get an XBox (more games and similar "oohh, shiny" graphics)
Slashdot Mirror
One of the really nice things about Google maps is the same API is used for google maps and google earth. Well, maps uses a subset.
So you can easily do pretty-ultra-eyecandy that also works well when viewed just through the web.
Isn't the iPhone basically what the Newton was supposed to be, but with a soft-keyboard rather than text recognition (which could be added to 2.0 easily enough)?
(which I can, BTW, I stole my dad's many years ago, but I think it got lost in a random move), do you know WHY a slide rule works, and how to make a slide rule for addition and subtraction...
Thats what the Bloom filter suggestion was, but the bloom filter is better because its a small amount of data you store locally, and then only do you send a query to google.
The GPLv3 is full of FUD, a lot of it well founded. There is a reason I won't use it, but then even GPLv2 isn't as free as I like (BSD forever, yada yada yada)
This article is also FUD, and unlike other GPLv3 fun, it is NOT well founded.
That 6% are actually using GPLv3 already is not an indication of failure, but a pretty big success, and suprisingly high. That 40% will never touch GPLv3 is not suprising, because how many of them are BSD zealots rather than GPL zealots anyway.
Because privacy preserving database queries are different, and allow you to query the database WITHOUT the database owner able to extract information, and it is true "Deep crypto voodoo"
A hash is insufficient, as Google has constructed the hash and could just as easily keep a map of H(URL)->URL as part of the database.
Good idea. You'd have to stick to just the top level name and/or IP, but that would work.
I like it.
A "blacklist" of phishing sites needs to be stored somewhere, and you need to be able to do queries against it.
It changes too fast, and is too large, for it to be stored locally.
So SOMEBODY needs to provide a database interface to it, and unless you are willing to tolerate the voodoo cryptography and serious performance penalty to do privacy-preserving searches, how else is this supposed to be done?
Rather than just "Download file" you've got to download some random third party app to actually receive your music on MP3.
So what does it send, according to the FA:
The blog's URL
A list of all plugins and versions
A list of the $_SERVER env variables
How is this information not necessary for a robust autoupdating/autonotifying infrastructure? Since the plugns are the source of so many vulnerabilities, you need to know their versions etc.
Since so much incompatibility may be caused by funky $_SERVER variables, you need to know their contents.
And the blog URL tells you who it is.
Windows Update has to send far MORE intrusive information.
One thing: I occasionally travel to Europe.
There are two reasons I didn't get an IPhone a couple days ago:
The first is "all need landscape entry", as mentioned in the article.
The second is "WiFi Only mode": When out of AT&T, I don't want it to transmit data over the cell network, only on the WiFi. There is "airplane mode" (no net) and "no wifi mode", but there is no "no cell" mode that I was able to find in 15 minutes of trying with a demo unit.
Is there a game, with the exception of Wii Sports, that you've been thrilled that there's no option to go back to a regular d-pad?
Yes. Metroid Prime III
Yeah, the v3 Nano is cheaper to build. Its also cheaper to buy, with a 4 GB unit now $150 and $200 for the 8 GB, as opposed to 2 GB for $150, 4 GB for $200, and 8 GB for $250.
Not having the "Where you shoot is the middle of the screen" really ups the immersion factor. For enemies in view, the WiiMote is a VERY fast way to shoot them.
For strafing, the WiiMote/nunchuck controls are also really good, because the joystick is strafe not look. Likewies, the target-lock semantics (circle-strafe mode) work well.
So in many ways it is exactly like keyboard/mouse: look with the quick device (mouse/wiimote), and strafe/move with the keys.
I think the lesson of both the Wii and the DS is that for a lot of people, notably the non-gamers, FUN is what counts.
Technology, the PSP trashes the DS. The XBox360 makes the Wii look like a joke graphically and computationally.
But the new interfaces (touch screen, WiiMote) have lead to entirely new classes of games, and new ways of doing traditional games.
EG, after playing Metroid for a few hours, I can't see how anyone could go back to the classic FPS controls, especially on a console. On a DS, the touchscreen allows very rich UIs, which are not possible with just the D-pad and buttons.
That is the lesson from Nintendo: Fun Must Come First .
I was visiting an academic CS research group, which is doing some networking protocol work they want widely adopted (eg, in Windows would be a good start).
Their release of the prototype code was "whatever", so they did it under GPL (well, dual liscence, GPL for everyone, and a free liscence for funders). They were kind of shocked when the link on their web page was now pointing to a GPLv3 description, and I explained the implications.
They may very well change to BSD liscencing.
For FreeBSD, the kernel is BSD liscenced but pretty much all the tools are a mix of BSD and GNU v2 or later (and all from the FSF are GPLv3 soon), which is "hello GPLv3" for a lot of what you care about.
For Linux, the kernel is GPLv2 only but pretty much all the tools are the same mix of BSD and GNU v2 or later (and all from the FSF are GPLv3 soon), which is "hello GPLv3" for a lot of what you care about.
Thus there is no way GPLv3 will drive people from Linux to BSD for business use, as it really is the same impact for both.
A couple of other posters mentioned the state storing across power cycles. Being too lazy to read the paper in enough detail to create a slashdot question:
This shouldn't affect the fingerprinting, because you fingerprint on the highly-biased cells.
But how does this biasing effect interact with the true RNG operation? Have you done retention time experiments?
also, DRAM is worse on the retension time, but is it perhaps still suitable for the fingerprinting? Have you evaluated this yet?
the true RNG properties rely on the fact that:
a: Many of the bits are sorta random, but physically random. So very biased coins, but true randomness.
b: With the right reduction function, you can turn a LOT (eg, 512 Kb) of cruddy random data to a small amount (128b-512b) of very high quality, well distributed random.
And the fingerprinting relies on the fact that:
a: Many other of the bits are physically random, but VERY VERY biased. So map where those are and record them and it is a very good fingerprint. And since it is all silicon process randomness going into that, it is pretty much a physically unclonable function.
Kevin Fu has some SMART grad students.
Of course, the results will be edited to show that the 2,000,000th article is on Steven Colber's continuing humanitarian work to deal with the perpetual threat of BEARS!
Lets see, ~2% of the users run linux. What fraction of those are actually gamers?
Seems like a move more for the high-end workstation market.
As a gamer who plays, I'm currently enjoying Metroid on a Wii..
When I finally get an HDTV, My $$$ are going to the evil Borg empire (rather than the Evil sony empire) and getting an XBox 360 for Halo and GTA IV.
So why should anyone care about the PS3? The zealots who got them got them already, and all the rest are just not gonna care, get a Wii (gameplay) or get an XBox (more games and similar "oohh, shiny" graphics)
I always knew the FSF crowd were on some good drugs...
You have NNTP, the broadcast atomic clock information, and the cell-phone network, all of which provide exquisitly accurate time to everyone.