Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
NASA

The Sun Unleashes Coronal Mass Ejection At Earth 220 220

astroengine writes "Yesterday morning, at 08:55 UT, NASA's Solar Dynamics Observatory detected a C3-class flare erupt inside a sunspot cluster. 100,000 kilometers away, deep within the solar atmosphere (the corona), an extended magnetic field filled with cool plasma forming a dark ribbon across the face of the sun (a feature known as a 'filament') erupted at the exact same time. It seems very likely that both eruptions were connected after a powerful shock wave produced by the flare destabilized the filament, causing the eruption. A second solar observatory, the Solar and Heliospheric Observatory, then spotted a huge coronal mass ejection blast into space, straight in the direction of Earth. Solar physicists have calculated that this magnetic bubble filled with energetic particles should hit Earth on August 3, so look out for some intense aurorae — a solar storm is coming."

Comment Re:Possible Solution (Score 1) 932 932

I use a similar system for personal use but I do not have it wipe all the data on each restart, instead I just wait for the system to start getting a bit sluggish or I am ready for a clean start and restore the original virtual machine. Still kind of a pain but so much better then restoring your whole system. I have been using this setup for a couple years and I have not had to reformat my main system.

Comment Where do I put the fish again? (Score 4, Funny) 133 133

Parece que he perdido mi copia de la guía, pero como yo soy un príncipe de Nigeria, con mucho gusto a comprar uno por $ 10 millones de dólares EE.UU., si usted me ayudará a transferir fondos de mi hermano, que ha robado mi difunto padre trono. Por favor, responda con su información bancaria para que podamos ayudarnos mutuamente.

Comment Re:DRM Keys (Score 1) 151 151

Yes, I am familiar with that idea... the point however is access control. How do you decide the X lucky recipients of your partial key? How do you assume they are trustworthy? Then again, if you're not watching the logs, how to you know they aren't cheating the system, and trying to assemble the full key without your permission?

The whole point of DRM is to give permission when you wish. Any system that allows someone to skip asking permission, and later beg forgiveness is broken. In that same vein, any DRM system gives you the keys at some point, and says "do not unlock this door"; therefore it always fails, even if we use it simply because it's easier to ask then to beg permission.

Comment DRM Keys (Score 3, Insightful) 151 151

Perhaps I missed this in the TFA, but how exactly do they plan on actually releasing the keys? The whole point of DRM is to keep the keys out of your reach. I cannot think of a single, viable way to hide the key exchange without some black-box single point of distribution. Sure you can distribute the encrypted content via P2P... but unless the keys are decentralized as well... calling it a P2P system is just a touch disingenuous.

The key-servers still will represent a single point of failure, and a single point of ownership. Now we'll just pay for most of the bandwidth instead of them.

Software

Smarter Clients Via ReverseHTTP and WebSockets 235 235

igrigorik writes "Most web applications are built with the assumption that the client / browser is 'dumb,' which places all the scalability requirements and load on the server. We've built a number of crutches in the form of Cache headers, ETags, and accelerators, but none has fundamentally solved the problem. As a thought experiment: what if the browser also contained a Web server? A look at some of the emerging trends and solutions: HTML 5 WebSocket API and ReverseHTTP."

Comment Re:Someone doesn't get data compression (Score 1) 731 731

Well, writing on DEC hardware, most of the assembly instructions could be morphed by bit shifting into something else, useful, for example a Pointer Jump was just an overflow from a Jump Not Equal, so you could *cough* theoretically write an infinite looking loop that would exit when a strategically placed variable was overflowed. Thank god people don't write like that now, but when you had a 16k address space to work with, tricks like that were, well indispensable. As for the byte shifting, on a PDP, a bitwise shift (because most instructions began with a null byte) was a fast operator, rather than having to run a real decompressor.

Thinking about this, I miss the Good Old Days(tm).

You are in a maze of little twisting passages, all different.

Working...