Follow Slashdot blog updates by subscribing to our blog RSS feed


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:Just Another Symptom (Score 0) 64

Just another symptom of a fundamentally fucked up system of justice.

If a peon employee does this he'd get dragged into court, but some fucked up high society brown nose asshole can fraudulently misrepresent his employment status and breach his contract with a small sideways glance.

Your description of an assistant editor at some half remembered website as 'high society' makes me wonder at just how far down the food chain you happen to be.

It must really suck to be you.

Comment Just start syndication (Score 1) 173

Krebs just needs to change his distribution model. Instead of limiting this info to his own website, just start publishing the content on any interested website. Why hasn't slashdot already contacted him and offered to host his content? Even if they can DDoS a single major site into submission, they won't stand a chance of taking several offline.

For that matter, why wasn't Akamai sending out tons of abuse@ emails during this mess, telling ISPs to stop the flood coming from their side, or face financial liability for any continuing traffic? That would actually SOLVE the DDoS problem, quickly and permanently diminishing the ranks of their botnets, and eliminating the attackers resources, costing them money.

Comment Re:They HAD this service? (Score 1) 48

Start shooting in RAW mode. You'll hit a terabyte before you know it. Better yet, get a 5D Mark IV and use Dual-Pixel RAW so that 5% more image data can take 100% more space. I mean, you'd think they would have used sum-difference encoding, sign-magnitude encoding (with a single-bit right rotation so the sign bit is on the right), and bitwise run-length encoding (all the top-order bits first) to make that file format efficient, but instead, they encoded the sum of the two images followed by one of the two images by itself, both using lossless JPEG. I can't imagine what they were thinking. The impact of dual-pixel RAW should have been an order of magnitude less than it is.

Comment Re:Am I reading this right? (Score 1) 64

The weird thing, if it is the COPVs, is... there was so much attention focused on them after CRS-7. It'd be weird if this was the cause. And extremely frustrating, too, as they're not manufactured in-house. SpaceX surely tests the tanks, so they too would bear some responsibility for it getting past their test procedures, if this is the cause. Personally (as I mentioned elsewhere in the comments), having a composite vessel sitting in liquid oxygen always strikes me as a dangerous situation to begin with.... if we were good at maintaining LOX-composite compatibility, we'd be making the stages themselves out of composites rather than aluminum.

Of course, the COPVs aren't the only part of the "helium pressurization system". Still concerning that whatever it was slipped past them.

Comment Re:Huh. (Score 3, Interesting) 64

The helium isn't used for cooling; it's a pressurant. It's lower mass to make a small COPV and have that store your pressurant in it than to have the whole LOX tank be strong enough to withstand the pressure.

It's always bothered me, the concept of having a COPV sitting around in LOX, though. Ignoring the thermal cycling, LOX and epoxy aren't exactly fast friends. We don't make LOX tanks out of composites because composites tend to become impact sensitive in LOX (there've been some attempts, but it's still an active reseach field, not a "solved problem"). Not sure there's that much difference between making your whole tank out of composites vs. having a composite tank inside of one. I don't know what SpaceX does, if anything, to try to protect them, but the general concept has always concerned me.

Slashdot Top Deals

You had mail. Paul read it, so ask him what it said.