Perhaps what we need then is more specific moderating options. A way to use your mod points to disagree with other moderations on that post, or with the post itself. But don't just change the score, let individual users choose what score each option gets. Add a "Disagree" option, let me make it +1 instead of -1 so I can see both sides of the argument. Add an "Unfounded" or "Inaccurate" to counter those "Informative" and "Insightful" posts that *seem* right but aren't.
And give me a way to see all highly rated posts without seeing their low rated parent comments.
Mozilla *are* making huge changes under the hood. Back when 3 was the current version, they had *heaps* of new features and improvements slated for 4. But trying to fit them all into one big bang release just slowed down the process. Planning for more frequent releases allows those new under the hood improvements to be trickled in when each of them is finished.
Hi, I'm working for The Serval Project, and like other projects related to wifi mesh routing, we do have high level goals like this. And we're actively trying to make them a reality.
One of our staff just returned from a presentation to IEEE, to propose a more open standard for the next 802.11 spec.
The basic premise of our proposal is that the protocol for using wifi devices to route traffic should be dealt with in kernel or user space. Not in the radio spec. And that adhoc, and 802.11s are useless for this task (Damn you BSSID, why you change?). We also think that security and perhaps even error correction should be dealt with via a VPN or baked into the application layer.
We want the next wireless spec to include a basic packet radio mode, operating in any unlicensed white-space spectrum, that gives as much control as possible to higher levels of the OS. So that new interesting ideas are easier to experiment with and implement.
And we've been invited to the next IEEE working group to help make it happen.
So google already have local caches, and respond to DNS queries with your local cache's IP address. Just like Akami and other content networks do.
But some global DNS services like OpenDNS will do the lookup once, getting an IP for a cache that is local to their service, and return that IP address to all users.
So google and OpenDNS came up with a DNA protocol extension so that end users get the right address.
I'm working with The Serval Project attacking this same kind of communication problems from a different direction. Our focus is building a phone network with smart phones using their wifi radios. Back in June I spent a couple of days with Alexander Chemeris hacking OpenBTS and Serval's DNA together to route a GSM phone call over a wifi mesh network to one of our android phones, that was a fun couple of days.
At some point soon we'd like to tackle the problem of phone number registration on a network of OpenBTS & Serval based devices, and assist in providing a connection to the global phone network. We'd also like to replace SIP as it isn't ideal for bandwidth constrained connections like satellite links.
Huh, by encoding some information in silences, you can tell if anyone is trying to drown out your signal. So if you hear a TEA transmission and respond to it, you can establish a secure link back to the sender. That seems reasonably achievable and could provide better link layer security than WEP or WPA for unicast traffic. Though it does require custom code to be implemented in each wifi driver, or in some cases perhaps in firmware.
But this approach doesn't directly give you a way to authenticate the person you are talking to. Without authentication you can disable the radio of the victim, and then impersonate them.
But also from that picture, the flat panel array is on the ground and partially covered by shadow from some nearby tree's. That difference alone might account for the increase.
That's a 135TB, *4U* server. And I was counting 2^88 data storage as bits not bytes, though I'm not sure if the paper specifies the size of a data object anywhere.
So (( 2^32 / 8 ) * 20' * 8' )^1/2 = 293K feet per side.
The blackblaze is a full length server case, so you wouldn't fit 1400 of them into the 40' container.
135TB in a 4U Blackblaze storage pod, 280 rack units in a 20' x 8' [... x 8' high? ] shipping container, gives 9.5PB or log2(135 * 8 * 10^12 * 280 / 4) 2^56 bits of raw online storage.
So now you *only* need 4 billion (2^32) shipping containers... yeah right. Stacking them 8 high, with no space for walkways or roads, would cover an area at least 55 miles on each side.
Modern currencies are backed by the banks which issue them.
FTFY. Most "currency" in circulation these days is just numbers in bank accounts. Which arrived there as deposits paid from loans or credit cards. Backed by the bank's asset ledger, which includes a significant percentage of housing loans...
Cash, printed and / or issued by the government or central bank is insignificant in comparison.
Yep, fraud enables the creation of bad debt. But this problem is bigger than that. The western worlds appetite for more debt has been insatiable. Any legitimate sounding scheme that could be invented to fuel that appetite would have worked.
The economy stopped being about true investment a long time ago, instead it turned into a massive ponzi scheme. Asset prices were inflated by easy credit, and those rising asset prices enabled more credit to be issued. One market after another reached a level of debt saturation, and time and again the financial industry simply moved on to the next sucker. A vicious spiral leading to an inevitable systemic failure when they ran out of greater fools.
And you can't really blame all the players in this game, since the rule book they are all following says that the total debt level in the system is irrelevant. They were all oblivious to the elephant in the room, right up to the point it stampeded, and even now only a few economist grudgingly admit its existence.
With our 20/20 hindsight view of what happened, and our forensic analysis of what went wrong, it's obvious to us now that these models were grossly flawed and doomed to fail as they did. But this isn't a great big evil conspiracy. Just blind ignorance and faith in a completely broken model of economics. This is the inevitable consequence of trusting your model of the world more than you trust your own eyes.
I highly recommend reading the work of Steve Keen, who's Debunking Economics book and Behavioural Finance lecture series, systematically destroy just about every model that economist hold dear. Who started publicly predicting our demise at least before 2006.
Misusing statistics certainly enabled this crisis. And you can certainly point at these failures to explain why the whole house of cards collapsed when it did. But I wouldn't say this was the cause.
The pile of debt in our economy has been growing exponentially since the mid 60's. It was inevitable that we would eventually reach saturation and our debt growth would stop and then reverse.
You can point to CDS's and other invented financial instruments for delaying the inevitable crash and making the problem worse. But any vehicle that increased leverage could have replaced them.
For running on HD's I think there should be one OS with one picture of the filesystem. So that caching, prioritisation and request reordering can all occur in one place, with as much information about the immediate future as possible. Each VM should then import a section of that filesystem. But if you're talking about databases, they tend to replace most of the filesystem level caching anyway, so you'd still be better off with SSD's and / or dedicated storage.
Slashdot Mirror
Perhaps what we need then is more specific moderating options. A way to use your mod points to disagree with other moderations on that post, or with the post itself. But don't just change the score, let individual users choose what score each option gets. Add a "Disagree" option, let me make it +1 instead of -1 so I can see both sides of the argument. Add an "Unfounded" or "Inaccurate" to counter those "Informative" and "Insightful" posts that *seem* right but aren't.
And give me a way to see all highly rated posts without seeing their low rated parent comments.
Mozilla *are* making huge changes under the hood. Back when 3 was the current version, they had *heaps* of new features and improvements slated for 4. But trying to fit them all into one big bang release just slowed down the process. Planning for more frequent releases allows those new under the hood improvements to be trickled in when each of them is finished.
And if you can't get a job directly in line with your chosen career, do something on the side to improve your skills and experience in that area.
Why else do you think 2.4 Ghz wifi is unlicensed spectrum? It's mainly *because* microwaves make it useless for much else.
Hi, I'm working for The Serval Project, and like other projects related to wifi mesh routing, we do have high level goals like this. And we're actively trying to make them a reality.
One of our staff just returned from a presentation to IEEE, to propose a more open standard for the next 802.11 spec.
The basic premise of our proposal is that the protocol for using wifi devices to route traffic should be dealt with in kernel or user space. Not in the radio spec. And that adhoc, and 802.11s are useless for this task (Damn you BSSID, why you change?). We also think that security and perhaps even error correction should be dealt with via a VPN or baked into the application layer.
We want the next wireless spec to include a basic packet radio mode, operating in any unlicensed white-space spectrum, that gives as much control as possible to higher levels of the OS. So that new interesting ideas are easier to experiment with and implement.
And we've been invited to the next IEEE working group to help make it happen.
No they wont, they don't have to. They'll focus on how different these metal membranes are from actual life.
Of course application developers will also need to compile any native code they have.
Phoronix should be ashamed...
That goes without saying though.
So google already have local caches, and respond to DNS queries with your local cache's IP address. Just like Akami and other content networks do.
But some global DNS services like OpenDNS will do the lookup once, getting an IP for a cache that is local to their service, and return that IP address to all users.
So google and OpenDNS came up with a DNA protocol extension so that end users get the right address.
I'm working with The Serval Project attacking this same kind of communication problems from a different direction. Our focus is building a phone network with smart phones using their wifi radios. Back in June I spent a couple of days with Alexander Chemeris hacking OpenBTS and Serval's DNA together to route a GSM phone call over a wifi mesh network to one of our android phones, that was a fun couple of days.
At some point soon we'd like to tackle the problem of phone number registration on a network of OpenBTS & Serval based devices, and assist in providing a connection to the global phone network. We'd also like to replace SIP as it isn't ideal for bandwidth constrained connections like satellite links.
Domains matching your search criteria would probably rate highly though...
Huh, by encoding some information in silences, you can tell if anyone is trying to drown out your signal. So if you hear a TEA transmission and respond to it, you can establish a secure link back to the sender. That seems reasonably achievable and could provide better link layer security than WEP or WPA for unicast traffic. Though it does require custom code to be implemented in each wifi driver, or in some cases perhaps in firmware.
But this approach doesn't directly give you a way to authenticate the person you are talking to. Without authentication you can disable the radio of the victim, and then impersonate them.
"Hello this is Raji, it's time to wake up. Can I interest you in a new phone plan?"
But also from that picture, the flat panel array is on the ground and partially covered by shadow from some nearby tree's. That difference alone might account for the increase.
That's a 135TB, *4U* server. And I was counting 2^88 data storage as bits not bytes, though I'm not sure if the paper specifies the size of a data object anywhere. So (( 2^32 / 8 ) * 20' * 8' )^1/2 = 293K feet per side.
The blackblaze is a full length server case, so you wouldn't fit 1400 of them into the 40' container.
135TB in a 4U Blackblaze storage pod, 280 rack units in a 20' x 8' [ ... x 8' high? ] shipping container, gives 9.5PB or log2(135 * 8 * 10^12 * 280 / 4) 2^56 bits of raw online storage.
So now you *only* need 4 billion (2^32) shipping containers... yeah right. Stacking them 8 high, with no space for walkways or roads, would cover an area at least 55 miles on each side.
http://www.debtdeflation.com/blogs/2009/01/31/therovingcavaliersofcredit/
Modern currencies are backed by the banks which issue them.
FTFY. Most "currency" in circulation these days is just numbers in bank accounts. Which arrived there as deposits paid from loans or credit cards. Backed by the bank's asset ledger, which includes a significant percentage of housing loans...
Cash, printed and / or issued by the government or central bank is insignificant in comparison.
But they also need a fairly stable value. Or at least the perception of stability.
Or they can buy the “Bought This Bitcoins Badge With Bitcoins” badge with Bitcoins.
Yep, fraud enables the creation of bad debt. But this problem is bigger than that. The western worlds appetite for more debt has been insatiable. Any legitimate sounding scheme that could be invented to fuel that appetite would have worked.
The economy stopped being about true investment a long time ago, instead it turned into a massive ponzi scheme. Asset prices were inflated by easy credit, and those rising asset prices enabled more credit to be issued. One market after another reached a level of debt saturation, and time and again the financial industry simply moved on to the next sucker. A vicious spiral leading to an inevitable systemic failure when they ran out of greater fools.
And you can't really blame all the players in this game, since the rule book they are all following says that the total debt level in the system is irrelevant. They were all oblivious to the elephant in the room, right up to the point it stampeded, and even now only a few economist grudgingly admit its existence.
With our 20/20 hindsight view of what happened, and our forensic analysis of what went wrong, it's obvious to us now that these models were grossly flawed and doomed to fail as they did. But this isn't a great big evil conspiracy. Just blind ignorance and faith in a completely broken model of economics. This is the inevitable consequence of trusting your model of the world more than you trust your own eyes.
I highly recommend reading the work of Steve Keen, who's Debunking Economics book and Behavioural Finance lecture series, systematically destroy just about every model that economist hold dear. Who started publicly predicting our demise at least before 2006.
Misusing statistics certainly enabled this crisis. And you can certainly point at these failures to explain why the whole house of cards collapsed when it did. But I wouldn't say this was the cause.
The pile of debt in our economy has been growing exponentially since the mid 60's. It was inevitable that we would eventually reach saturation and our debt growth would stop and then reverse.
You can point to CDS's and other invented financial instruments for delaying the inevitable crash and making the problem worse. But any vehicle that increased leverage could have replaced them.
Much, much simpler solution, and probably just as simple to fake; require submission of your odometer reading when you renew your registration.
Better game gets downloaded more, well duh.
For running on HD's I think there should be one OS with one picture of the filesystem. So that caching, prioritisation and request reordering can all occur in one place, with as much information about the immediate future as possible. Each VM should then import a section of that filesystem. But if you're talking about databases, they tend to replace most of the filesystem level caching anyway, so you'd still be better off with SSD's and / or dedicated storage.