Please create an account to participate in the Slashdot moderation system

 



Forgot your password?
typodupeerror
×

Comment What have they done (other than lose your data)? (Score 1) 1

You haven't mentioned what your contractor has done to limit your exposure in this case, have they offered free credit monitoring to those affected?

If so, that would make things "a little less wrong": in my eyes.

Here is a situation report that would make such an event "more right" to me

                        time = ungodly early hour of the morning (ie 7am)

ring RING ring

ME: oighewhhnweeruhhhhhhhhuuummmmm....

THEM: Sorry to wake you , we had a break in last night at one of our employees homes while they were away at a movie, and they took all the valuables in the home, including your data.

ME: What have you done about it, what are you doing about it, what are you going to do?

THEM: The data was mounted on an encrypted o/s , and our person still have the encryption key around his neck, so that part is secure, your data was mounted on a software raid0 put across 4 usb drives that were encrypted with a different key (also safe) , not only was the database encrypted, but all non public data (like id numbers, ss numbers) was further encoded/encrypted.

The lowjack on the laptop started reporting once it was removed from the firesafe it was stored in, and our goon squad captured the thief, and he quickly invited his companions over. We have recovered most of the physical equipment, and are continuing to dismember the miscreants to ensure that they are nothing more than teenage hoodlums.

ME: Do I know any of them, are any linked to my company in any way?

THEM: We believe that this was a targeted crime on this house, and its marketable contents, not at your data or your project. They do not know who you, or what your project is.

ME: Anything else?

THEM: We will offer a full 2 years of active credit fraud monitoring to all affected persons, and will reimburse anyone for all reasonable expenses, such as new checks, or fraudulent activity.

ME: Sounds like its all taken care of, I will want a full report by the end of day.

THEM: No problem.

If they hit all the points above, then they go to the "preferred vendor list", because they can handle problems that crop up, and I know my stuff is safe with them. Anything less, and I start taking points away.

If they haven't done diddlily , ill sue them to provide notification and credit monitoring for those affected.

Government

Submission + - Firefox Plugin Liberates Paywalled Court Records (recapthelaw.org)

Timothy B. Lee writes: "If you want to access federal court records, you're often forced to use PACER, a cumbersome, paywalled website run by the federal judiciary. My colleagues and I at Princeton's Center for IT Policy have released a new Firefox extension called RECAP that allows users to automatically upload the documents they download from PACER into a public archive hosted by the Internet Archive. It also saves users money by automatically notifying them if a document they're searching for is available for free from the public archive. Over time, we hope to build a comprehensive, free repository of federal court records that's available to everyone."

Comment Re:WTF? Oh wait, I forgot about magic bit... my ba (Score 1) 4

the savings that you are talking about are so small, compared to the bandwidth we have today,it is beyond silly to look for savings compressing the http header.

If everyone had a 300 baud modem (0.3 kbit/s http://www.youtube.com/watch?v=X9dpXHnJXaE&eur ), THEN I could see doing something like this, but this is not 1964, the unused bandwidth in our connections is massive compared to the "savings" of such a scheme.

please get a packet sniffer, such as wireshark, or a local HTTP proxy (charles or fiddler) this will allow you to understand the larger picture. once you see how insignificant the HTTP headers are, in the total transmission of data, let alone compared to the size of most broadband pipes out there, it is not even close.

the traffic on the Internet was constructed so that people could read and debug the output using the simplest of tools, and require a little bit of knowledge, and not a bunch of "stuff" between the person trying to figure out what is not working, and the data. Take a look at how microsoft stores email, and how thunderbird does. When the mail spool gets out of sync, guess the one ya can open with a text editor and fix. Guess the one that gives you a "tool" to try and automagicily fix most of the common errors, that sometimes "mostly works".

there is a old school fortune message that should help you out...
http://buffy.sighup.org.uk/hfiles/aalg.html
    A famous Lisp Hacker noticed an Undergraduate sitting in front of a
    Xerox 1108, trying to edit a complex Klone network via a browser.
    Wanting to help, the Hacker clicked one of the nodes in the network
    with the mouse, and asked "what do you see?" Very earnestly, the
    Undergraduate replied "I see a cursor." The Hacker then quickly
    pressed the boot toggle at the back of the keyboard, while
    simultaneously hitting the Undergraduate over the head with a thick
    Interlisp Manual. The Undergraduate was then Enlightened.
  ( http://www.canonical.org/~kragen/tao-of-programming.html )

until the above koan is understood, lets try something more tangible, how about we see what is happening with some of the traffic. lets assume 160 bytes (payload) per packet , 1 char per byte (for the sake of the non technical people following along), and look at what is happening (space wise).

the http header that you give in your example contains 247 characters,
spanning 2 packets. The second packet follows about 2ms (high average)
after the first, so this saves you 1 packet per request, and 2ms
per http header request, for a grand total of 28ms and 14 packets.

your web page infinity-infinity.com/2009/06/making-the-internet-faster-in-5-minutes/
has 14 http header requests, (results in BYTES ).

GET http://infinity-infinity.com/2009/06/making-the-internet-faster-in-5-minutes/
Request Count: 1
Bytes Sent: 545
Bytes Received: 10,869
Requests started at: 21:15:48:3700
Responses completed at: 21:15:50:7720
Aggregate Session time: 00:00:02:4020
Sequence (clock) time: 00:00:02.4020000
TCP/IP Connect time: 452ms
        RESPONSE BYTES (by Content-Type)
  ~headers: 328
text/html: 10,541

GET http://infinity-infinity.com/wp-content/plugins/sociable/sociable.css
Request Count: 1
Bytes Sent: 451
Bytes Received: 1,145
Requests started at: 21:15:50:8640
Responses completed at: 21:15:51:1610
Aggregate Session time: 00:00:00:2970
Sequence (clock) time: 00:00:00.2970000
        RESPONSE BYTES (by Content-Type)
~headers: 293
text/css: 852

GET http://infinity-infinity.com/wp-content/themes/fancy/style.css
Request Count: 1
Bytes Sent: 444
Bytes Received: 22,123
Requests started at: 21:15:50:8840
Responses completed at: 21:15:56:2780
Aggregate Session time: 00:00:05:3940
Sequence (clock) time: 00:00:05.3940000
TCP/IP Connect time: 156ms
        RESPONSE BYTES (by Content-Type)
~headers: 297
text/css: 21,826

GET http://infinity-infinity.com/logo.png
Request Count: 1
Bytes Sent: 419
Bytes Received: 1,051
Requests started at: 21:15:51:3650
Responses completed at: 21:15:55:7770
Aggregate Session time: 00:00:04:4120
Sequence (clock) time: 00:00:04.4120000
TCP/IP Connect time: 3,136ms
        RESPONSE BYTES (by Content-Type)
  ~headers: 277
image/png: 774

GET http://infinity-infinity.com/wp-content/themes/fancy/img/banner.gif
Request Count: 1
Bytes Sent: 449
Bytes Received: 46,634
Requests started at: 21:15:51:6340
Responses completed at: 21:16:09:3600
Aggregate Session time: 00:00:17:7260
Sequence (clock) time: 00:00:17.7260000
        RESPONSE BYTES (by Content-Type)
image/gif: 46,355
  ~headers: 279

GET http://pagead2.googlesyndication.com/pagead/show_ads.js
Request Count: 1
Bytes Sent: 437
Bytes Received: 408

GET http://infinity-infinity.com/wp-content/themes/fancy/img/feed-green.gif
Request Count: 1
Bytes Sent: 453
Bytes Received: 1,178
Requests started at: 21:15:52:3720
Responses completed at: 21:15:59:6340
Aggregate Session time: 00:00:07:2620
Sequence (clock) time: 00:00:07.2620000
TCP/IP Connect time: 3,105ms
        RESPONSE BYTES (by Content-Type)
image/gif: 901
  ~headers: 277

GET http://infinity-infinity.com/wp-content/themes/fancy/img/scissors-green.gif
Request Count: 1
Bytes Sent: 457
Bytes Received: 621
Requests started at: 21:15:51:1710
Responses completed at: 21:15:51:3510
Aggregate Session time: 00:00:00:1800
Sequence (clock) time: 00:00:00.1800000
        RESPONSE BYTES (by Content-Type)
image/gif: 345
  ~headers: 276

GET http://infinity-infinity.com/wp-content/plugins/wp-syntax/wp-syntax.css
Request Count: 1
Bytes Sent: 453
Bytes Received: 1,028
Requests started at: 21:15:51:3610
Responses completed at: 21:15:51:5340
Aggregate Session time: 00:00:00:1730
Sequence (clock) time: 00:00:00.1730000
        RESPONSE BYTES (by Content-Type)

~headers: 293
text/css: 735

GET http://infinity-infinity.com/wp-content/themes/fancy/img/bg/bg.gif
Request Count: 1
Bytes Sent: 448
Bytes Received: 341
Requests started at: 21:15:56:3280
Responses completed at: 21:15:56:4350
Aggregate Session time: 00:00:00:1070
Sequence (clock) time: 00:00:00.1070000
        RESPONSE BYTES (by Content-Type)
image/gif: 67
  ~headers: 274

GET http://infinity-infinity.com/wp-content/themes/fancy/img/sep.gif
Request Count: 1
Bytes Sent: 446
Bytes Received: 320
Requests started at: 21:15:56:4080
Responses completed at: 21:15:57:4970
Aggregate Session time: 00:00:01:0890
Sequence (clock) time: 00:00:01.0890000
TCP/IP Connect time: 109ms
        RESPONSE BYTES (by Content-Type)
image/gif: 45
  ~headers: 275

GET http://infinity-infinity.com/wp-content/themes/fancy/img/sep-green.gif
Request Count: 1
Bytes Sent: 452
Bytes Received: 320
Requests started at: 21:15:56:4160
Responses completed at: 21:15:57:2150
Aggregate Session time: 00:00:00:7990
Sequence (clock) time: 00:00:00.7990000
TCP/IP Connect time: 110ms
        RESPONSE BYTES (by Content-Type)
image/gif: 45
  ~headers: 275

GET http://infinity-infinity.com/wp-content/themes/fancy/img/clock.gif
Request Count: 1
Bytes Sent: 448
Bytes Received: 883
Requests started at: 21:15:56:4450
Responses completed at: 21:15:56:6310
Aggregate Session time: 00:00:00:1860
Sequence (clock) time: 00:00:00.1860000
        RESPONSE BYTES (by Content-Type)
image/gif: 607
  ~headers: 276

GET http://infinity-infinity.com/wp-content/themes/fancy/img/person.gif
Request Count: 1
Bytes Sent: 449
Bytes Received: 1,280
Requests started at: 21:15:56:6410
Responses completed at: 21:15:56:8880
Aggregate Session time: 00:00:00:2470
Sequence (clock) time: 00:00:00.2470000
        RESPONSE BYTES (by Content-Type)
image/gif: 1,003
  ~headers: 277

GET http://infinity-infinity.com/wp-content/themes/fancy/img/folder.gif
Request Count: 1
Bytes Sent: 449
Bytes Received: 1,246
Requests started at: 21:15:56:8980
Responses completed at: 21:16:00:2590
Aggregate Session time: 00:00:03:3610
Sequence (clock) time: 00:00:03.3610000
        RESPONSE BYTES (by Content-Type)
image/gif: 970
  ~headers: 276

the only thing (from your web sever) that gets loaded when people hit a different article is the main page (and new graphics/elements). all the other previously used subsets (css,gifs, etc) get loaded from cache, so for each "new" viewing you only save 1 packet, unless the minimum time has expired (4 hrs) and the browser hits the web server with a header request.

if you run tidy on your HTML, you will save a bunch of space,
even if you run gzip compression...

tracking-visitors-mouse-movements/
old 25850 post tidy 25059

10-php-functions-you-probably-never-use/
old 51688 post tidy 49805

will-google-chrome-os-be-a-webos/
old 28392 post tidy 27595

you get the picture, if you open your .css files, you will notice a HUGE amount of comments that do not need to be transmitted, for example in your themes/fancy/style.css (this is not compressed with gzip), you could chop put the "fancy discription", saving you over 1500 characters, or 9 packets, or 10-20ms. If 20ms is no big deal, nor is %0.01 of my bandwidth, then leave your "fluff" in your content.
This is a great example of the fluff that can be removed.

Theme Name: Fancy
Theme URI: http://www.azmoney.co.uk/wordpress-themes/fancy
Description: "Fancy" is a free WordPress theme which really lets your blog stand out from the crowd. Make your blog unique by changing the main blog color (pink, yellow, green), background pattern (available over 20 background variations), banner etc through an options page. In addition you have the ability to choose the color of sidebar blocks (violet, yellow, green). Tech folks might find interesting that we built this theme based on css framework "Blueprint". Valid CSS & HTML. Designed by a href= h tp: www.azmoney.co.uk AZ Money a Web Design.
(blah blah blah, you get the point)

Comment WTF? Oh wait, I forgot about magic bit... my bad.. (Score 1) 4

Ok, so you get all the browsers and web servers to change the
way to do things, overnight and by magic, %100 compliance.

You don't make "the Internet faster" because HTTP headers make
up WAY less than %0.01 of the Internet traffic as a whole. If you
want to "make web pages display to the user faster" (there is
more to the Internet than port 80, 81, 443, 3128, 8000, and 8080)
make stupid graphics more cache friendly , place more/better
caches in an ISP's infrastructure, eliminate dynamically
generated static content, and have browsers support
SRV (RFC 2782 http://www.faqs.org/rfcs/rfc2782.html ) .

You also break packet sniffers,proxies, filter rules, and heaps of
other things that count on things that follow RFC standards.
Oh wait, I forgot about magic bit... my bad...

SRV record support would give you a MUCH better web page
viewing experience than rewriting a whole protocol. Its only
been about 10 years since SRV was thought up, and its more
doable than having a one letter substitution on standard replies.

If you point is to reduce number of packets sent across the
net why not put a 4 alpha/num code (a-z A-Z 0-9)for all the tags, that
will give you over 1,300,000 "tags" vs verbose stuff like
__ DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "blah://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.duh
that saves boatloads of space right there. WAY more than the
HTTP headers take up, and since the main HTML page crosses
packet boundaries, you will be reducing the packets transmitted
across the Internet. Those space savings WILL (mostly) cross the
packet boundaries, unlike the HTTP header.

While I applaud your desire to "make the Internet faster" please be
clear that web servers are a small subset of the total Internet traffic,
and HTTP headers are a MUCH smaller bit than that.

Lets travel back in time, pre torrent, around 10 years ago, when the
HTTP was the "biggest clog in the tubes", it made up around %70-%75
of the traffic as a whole.
http://www.isoc.org/inet98/proceedings/6g/6g_3.htm
Your talking about shaving 1 packet off of EACH transaction
AT THE MOST. Each "normal" packet ranges in size from
a few hundred bytes, to 1500, anything in that range is one packet.

Your scheme only "saves packets" when multiple packets are sent
out in the HTTP response, AND when your "savings" crosses
the packet boundary, a rare case.

The web page that you wrote
  http://infinity-infinity.com/2009/06/making-the-internet-faster-in-5-minutes/
is over 100k, smaller than the average web page,
http://interface.missouri.edu/2008/05/average-web-page-size-triples.php
and at MOST you are talking about getting a 1k reduction in web
traffic.

If you bothered to run a simple HTML cleaner (tidy) on the web page,
http://infinity-infinity.com/2009/06/making-the-internet-faster-in-5-minutes/
you would save over 7,000 characters , over 10x more than
if everybody adopted your new and magical standard.

Lets take a look at a well written compact web page, www.lois.org ,
it is under 6,000 bytes, yours is over 140,000 bytes. Your raw
HTML is sloppy and verbose. I find it disparaging that, if you
cleaned up your own web pages you would save more packets
than if "every one did things my new and improved way".

I think it would be most ironic if you scrunched up your output,
and then added all the compliance thumbnails, making the result
larger than the uncleaned original.

The Internet

Submission + - How to make the Internet faster in 5 minutes (infinity-infinity.com) 4

Brendon writes: "An article discusses and demonstrates the "cleaning up" of headers in the HTTP protocol, to reduce the bandwidth used to transfer useless data (such as words). By using shorter names for headers, eliminating the \r\n separator for constant values, where it is not needed, and choosing better representation of values, it is shown that up to 80% of data in a HTTP header is absolutely useless. This indicates that by removing the redundant information sent with this protocol, and others, the Internet could be made faster, at least a little. There is little reason why machines should be talking in "human language", as opposed to highly optimised and packed "machine language." Since a computer can not distinguish between "C" and "Content-Length", what advantage is there in using the latter? http://infinity-infinity.com/2009/06/making-the-internet-faster-in-5-minutes/"

Comment EFF Launches Surveillance Self-Defense Satellite (Score 1) 94

at first i thought the title said, "EFF Launches Surveillance Self-Defense Satellite", and i said, Cool those little bastards are gonna get whats coming to them. but no, it is a "Self-Defense Site", ok i can deal with that, its nice to know that the contributions that i have made over the years are going for rail gun rights. now i can look froward to a nice Phased-plasma rifle in the forty watt range. hmmm.... nope, nothing like that there.... and i did not find any mention of putting any of the people who allowed the data breach, did the breaching, or profited by the act ,into a game of "tay-zer tag" ( http://a.parsons.edu/~randy/tag/ ) what kind of lame "Self-Defense Site" is this?

Comment Re:They're not the first ... (Score 1) 259

Google will have some of the same issues as that "other startup",
and lots that are different. A floating oil platform
(to me) works better than a ship based datacenter.

_IF_ Google was to do a floating datacenter, I'd love to see
them take one of the old nuke flat-tops, and use that...
The big E as a datacenter would be killer, better than a pile of scrap.
http://www.defensetech.org/archives/003578.html
http://en.wikipedia.org/wiki/USS_Enterprise_(CVN-65)
http://www.nvr.navy.mil/nvrships/details/CV64.htm

EACH of the A2W power plants can deliver over 26,000 kw
(over 200,000 kw total) , and if you combine the reactor
hot water output, with an amonia based cooling system,
http://en.wikipedia.org/wiki/Einstein_refrigerator
http://www.nh3tech.org/absorption.html
can give low cost cooling.

Here is a letter that I sent to one of the VARS for the "other startup",
strangely enough, I never got an answer back. Perhaps it just got spam filtered out.

The questions remain unanswered....

*********** Mon Feb 4 11:23:17 2008
Received: from [****************.yahoo.com via HTTP; Mon, 04 Feb 2008 11:23:17 PST
Date: Mon, 4 Feb 2008 11:23:17 -0800 (PST)
**********************
Subject: Floating Data Centers?!?
To: ken@teamsilverback.com
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Content-Length: 8789

I saw your article about floating datacenters, and since you asked for
input, I thought I would chime in. Let me start off by saying I like the idea,
I know that there is great room for delivering a good product, at a good price point.

Now before I put my racks in a floating data center, here are some of my
concerns and references to real world issues. (I have a lot more, but
that depends on the ship and configuration.),

1) ""using sea water for their chill water"". Having seawater around is
a good heat sink, and since the ships are at dock most of the time, a long
pipe can be run to the cooler water zones to draw in water that is
close to freezing.
http://en.wikipedia.org/wiki/Deep_lake_water_cooling
Using colder sea water (after a standard air heat exchanger) can result in
good economies, if the heat exchangers can stand up to the corrosive environment.

2) ""All generators will have access to the ships fuel storage during disaster scenarios, which
allows them to operate for nearly a month without the need to refuel.""
    Traditional fuel for gen sets and large ship engines are very different. An
onboard gen set is like a modern rail road locomotive engine
(http://en.wikipedia.org/wiki/Image:3000hp_curve_ver2.jpg ), and it runs on diesel,
a main power plant for a ship (also a diesel) traditionally runs on Heavy Fuel Oil
(HFO). Without modifications to either the main power plant, or the gen sets, both
engines can not share the same fuel source. Please note the differences between #2
(the traditional fuel for ship board gen sets) , and #6 (Heavy Fuel Oil (HFO), AKA
Bunker C, the traditional fuel for ships manufactured in the 1980's). #6 is almost
a jelly at cold temperatures, and must be heated (to around 100c ) for efficient
movement, and burning. The main engine on a large cargo vessel is also much more
efficient (up to %50) in its use of fuel, making them more economical than the
smaller generators. Gen sets use a small amount of diesel per day, (compared
to the main engine) a 3100 kw gen set will use 4253 gallons of fuel per day
(http://www.antarctica.ac.uk/living_and_working/diaries/rrs_james_clark_ross/antarctic2000_2001/jrupdate86.php
) VS the very large ship engines at 1,660 gph of HFO ( http://people.bath.ac.uk/ccsshb/12cyl/ ).

3) ""able to quickly provide large scale real estate in some of the most real estate impacted
areas of the country."" Dock fees in some of those sections of the country can be
excessive, or what looks like good space can be unsuitable (silt, decaying Warf/dock ,
reserved space), and those spaces can be in some high crime zones. And while the
square footage is impressive, what matters is the gigawatts and gigabits that the
datacenter can throw around, these are dependent on the land based connections.

And now some of my own concerns.

Corrosion, poor ship building and maintenance
A report on the different kinds of corrosion how they occur, and how to detect them
http://www.ocimf.com/view_document.cfm?id=332

"of 29 fatal accidents involving bulk carriers between 1990 and 1994, 55% were due to plate
failure."

"According to Lloyd's September 1995 Shipping Economist, HTS (high-tensile (HT) steel) built ships
are also prone to a phenomenon known as "springing": because the ships are flexible and tend to
vibrate with short sea waves."

http://www.oceansatlas.com/unatlas/issues/safety/transport_telecomm/bulk_carrier/bulk99_una_2.htm

"In the early 1990s three carriers went down after their bows literally fell off. In other
instances, holes suddenly developed in carriers' hulls and some ships vanished without trace. One
bulk carrier that narrowly avoided this fate was the 24-year-old Gallant Dragon. In 1991 the ship
limped into port with a crack 50 metres long in its hull. It was scuttled shortly afterwards and
went down in 7 seconds."

"Last year the 139 000-tonne Diamond Sea, carrying a cargo of iron ore, was forced to put in for
repairs in Portugal with a 20-metre hole in its side. Another bulk carrier, the Protoklitos, was
scuttled, together with its cargo of iron ore, 400 kilometres off the coast of Brazil after it
became too badly damaged even to make the nearest port. And last November, at Ponta da Madeira in
northern Brazil, the Trade Daring broke its back while being loaded with iron ore."

"The best known of the bulk carrier losses is probably the Derbyshire, which went down in the
Pacific in 1980. But it was not a typical loss. The Derbyshire was only four years old, while most
bulk carriers that are lost are older. According to Intercargo, the average age of the carriers
lost between 1990 and 1994 was 18 years. And an investigation by the Australian parliament,
published in 1973, found that iron ore carriers over 15 years old were at the greatest risk of
sinking."

http://space.newscientist.com/article/mg14619752.200-clampdown-on-the-rust-buckets.html

"first-class ship maintenance has become increasingly rare in recent decades. Since the 1970s -
when the Erika, Nakhodka, and Castor were built - profit margins in the tanker business have
fallen steadily. Today, tankers change hands two or three times before they're taken out of
service. Temporary owners of second- or third-hand ships tend to be less interested in maintaining
their vessels than maximizing the return on their investments."
http://www.wired.com/wired/archive/10.06/superrust.html

"The plating of the oil tanker Castor corroded up to seven times faster than normal, causing
massive cracks across its deck that put the ship at risk of explosion or a hull rupture, the
American Bureau of Shipping has determined."
http://www.professionalmariner.com/ME2/SiteMaps/Sites/Document.asp?DocPath=4DEC050EBBB8412E8B2C27A67F745978%7C%7C%7CPublications%3A%3AArticle%7C%7C%7CMain%2BSite%7C%7C%7C

"The tanker being built today is flimsy, highly unreliable, unmaneuverable,
and nearly impossible to maintain. And the situation is becoming
progressively worse."

"Ship managers know that looks are
important. So they do enough chipping and painting to induce the
casual inspector to conclude that the ship is well-maintained. This
also allows them to send pretty pictures back to the owners showing
what a good job they are doing. But real maintenance, especially on
stuff that is not easily visible, is almost non-existent."

"If steel is found to be more than 25% wasted, then it must be replaced.41 Most
tanker owners let their steel deteriorate between Special Surveys and then
negotiate with the surveyor as to how much steel has to be replaced.
25% thickness loss is horribly wasted steel. Steel corrodes very
unevenly."

"The maritime press immediately announced that ABS had discovered a new
phenomenon which it dubbed "super-rust". There is no such thing. What
there is is the same old combination of poor maintenance, and understanding/
forgiving survey standards which eventually leads to a major hull failure."

"As soon as you tell an owner that a ship will be
worthless after age X, where X is any number less than 50, he will rightly
try and build a ship that is designed only to survive to age X. And if you
design a ship that can only survive to age X, you automatically have a ship
that will be a problem at age 0. An age restriction is an open invitation to
shoddy design. In order for a ship to be a good ship, it must be designed
to last forever."

http://www.c4tx.org/ctx/pub/tromedy2.pdf

Why use "end of life" commercial ships of unknown history, when stronger hulls ,
better overall constructed ships, and power plants that are converted to run on
light weight oils, are available for a low cost? (the mothball fleet).
http://hamptonroads.com/2008/01/dont-pay-us-well-pay-you-say-scrappers-ghost-fleet-ships

To me, a better option would be to refurbish the USS Constellation CV-64
(http://www.nvr.navy.mil/nvrships/details/CV64.htm ) , Ranger CV 61 (best choice) ,
or Independence CV 62 (to be sunk as a target because of poor construction practices) ,
these aircraft carriers have large long flat open spaces such as the sheltered
hangar deck and rooms below for lots of storage.

Tidal heaving, and wave action?
Storm damage?
Gen set loads, and load shedding.
Getting gigabit connections to a ship.
Getting enough electric power to a ship.
What happens when a ship must enter dry dock?
How will the hull be maintained?
Dock fires?
http://www.canada.com/victoriatimescolonist/story.html?id=e9b46da6-9af2-4178-a7c2-ebaa6129024c&k=85472

Security

Submission + - Is inexpensive video surveillance possible? 2

timholman writes: After a series of burglaries and auto break-ins in my neighborhood, I'm thinking about adding some video security cameras to my home. To me, the object isn't just deterrence — if someone tries to break into my house or my car (parked on the street in front of my house), I'd like to provide a high quality image of the perpetrator to give to the police. Inexpensive video surveillance systems are nearly useless, since the image quality is atrocious. The problem is being able to get good image quality at an affordable price. After some research, I've decided that using network cameras to FTP images to a central server over a HomePlug network is the best solution. However, good megapixel network cameras (e.g. Stardot or Axis cameras) can easily cost more than $1000 each. Has any Slashdotter dealt with a similar situation? Is there any way to get reasonable quality (preferably open source) video surveillance equipment for home use (daytime and nightime) without paying an arm and a leg? Is it better to go with a couple of expensive cameras, or a multitude of inexpensive cameras? Is paying two to three thousand dollars simply unavoidable if I want to monitor my front and back yards?
The Media

Submission + - Red scientology tomato rotting in Firehose? (slashdot.org) 1

An anonymous reader writes: A posting to the Slashdot Firehose related to a Wikinews story on Wikileaks and legal threats from Scientology, seems to be stuck in the Slashdot firehose red as a ripe tomato for more than 24 hours.
The story that covers a recent press release on Wikileaks relating to copyright claims made by the Church's legal representatives towards the published "Operating Thetan" cult manual, worth hundreds of thousands of dollars in scam money, already spawned a hot discussion on the Wikinews portal. With critics of cult-critics trying to shut the story down for hours, it finally went online. And now seems stuck in the Firehose. One can only hope not for the wrong reasons.

Medicine

A Virus that Attacks Brain Cancer 131

Ponca City, We Love You writes "In the past few years, scientists have looked to viruses as potential allies in fighting cancer. Now researchers at Yale University have found a virus in the same family as rabies that effectively kills an aggressive form of human brain cancer in mice. Using time-lapse laser imaging, the team watched vesicular stomatitis virus (VSV) rapidly home in on brain tumors, selectively killing cancerous cells in its path, while leaving healthy tissue intact. 'A metastasizing tumor is fairly mobile, and a surgeon's knife can't get out all of the cells,' says Anthony Van den Pol, lead researcher and professor of neurosurgery and neurobiology at Yale. 'A virus might be able to do that, because as a virus kills a tumor cell, it could also replicate, and you could end up with a therapy that's self-amplifying.' It's not yet clear why VSV is such an effective tumor killer, although Van den Pol has several theories. One possible explanation may involve a tumor's weak vascular system. Vessels that supply blood to tumors tend to be leaky, allowing a virus traveling through the bloodstream to cross an otherwise impermeable barrier into the brain, directly into a tumor."
Announcements

Submission + - Rackspace Dallas Data Center Totally Down

An anonymous reader writes: All power to the Rackspace Dallas hosting facility is lost. All client servers are down, including base camp, and any other servers in that facility. Here's the notice posted by Rackspace: Nov. 12th 9:30PM CST — As of 8:45 p.m. CST, temperatures are stabilizing in the DFW data center. In cases of servers that were proactively shut down to avoid overheating, we are starting the process of bringing the affected machines back online in a phased, gradual way. We are sorry for service disruptions caused by these events and understand how critical this is for your business. Throughout this process, we are making every effort to minimize impact on customer environments and return affected machines back to service as quickly and smoothly as possible. We continue to work with vendors to re-establish utility power to the facility and will keep providing updates here in the portal. Show Previous Updates Hide Previous Updates Nov. 12th 8:30PM CST — In a completely unrelated incident to this weekend's power problems in DFW, a traffic accident caused damage to a power transformer which provides utility power to our DFW data center. Here is the current sequence of events: * At approximately 6:00 p.m. CST utility power was lost to the DFW data center * Power automatically switched over to backup generators without disrupting service for any customers * When generator power was established two chillers within the data center failed to start back up * Utility power was re-established through a secondary utility source * As a result of temporary data center temperature increases, we proactively shutdown a number of customer servers to protect them from overheating At this point, the chillers are back up and running and we are operating on generator power throughout the data center. We have contractors on site to repair the damage and will be in contact with all customers who have been affected by this outage. We apologize for any disruption to your business operations and will work diligently to restore your service. Nov. 12th 8:00PM CST — Thank you for your patience today as we work through a root cause analysis of the power issues in the DFW data center. The Data Center Engineering team is continuing to work on the plan to move back to utility power without any further interruption in service. Rackspace will notify you in advance before we move to switch back to utility power. In the meantime, here is a brief timeline of events: Sunday, Nov. 11, 2007 * 4:19 a.m. CST — A problem in the internal utility power distribution grid caused an outage to cabinets in one section of the DFW data center. * 6:49 a.m. CST — Power was fully transferred to generator power. Based on building monitoring systems, outage times varied for every customer. DC engineering worked to isolate the internal utility problem and restore the integrity of the internal distribution system. * 6:32 p.m. CST — A separate incident occurred when a breaker in the generator power grid tripped, causing one of the Power Distribution Units (PDUs) in the same section of the DFW Datacenter to fail, affecting a much smaller group of the customers in this section. All customer devices with dual power supplies in this section of the datacenter remained online and were not affected. Customer devices with single power supplies in this area were affected. Data Center technicians immediately acted to minimize the impact on these customers by moving these devices manually to alternate power supplies — resulting in just a few minutes of downtime. * 7:40 p.m. CST — The breaker problem was diagnosed and resolved, bringing the down PDU back online. Monday, Nov. 12, 2007 * 4:00 a.m. CST — The Data Center engineering team had the initial utility distribution grid realigned and resynchronized. All systems reported ready for operation. * 4:30 a.m. CST — Transfer of power was initiated and affected devices were slowly moved off of generator power and back to internal utility distribution power. * 5:10 a.m. CST — Transfer of power was completed. * 5:25 a.m. CST — Unfortunately, the internal distribution grid failed again. Data Center engineering was able to transfer all affected devices back to generator power in under 15 minutes. * 5:40 a.m. CST — All affected devices were back on generator power. The Data Center environment is stable and is designed to be able to run indefinitely on generator power. Data Center engineering is continuing to diagnose the problem and engaging all vendors onsite. We will continue to provide updates via the MyRackspace portal. In addition, you will receive notification of any maintenance windows. We are committed to supporting your business and minimizing any impact on your hosted environment.
Music

Submission + - More RIAA Foolishness

budohorseman writes: "In an article posted on The Motley Fool financial web site titled Piracy 101: A Lesson in Suboptimal Lawsuits, Alyce Lomax covers the recent RIAA attempts to get colleges and universities to help them track down file sharing. She also goes on to describe how the RIAA sidesteps the DCMA, attempts to use 1984 laws that apply to cable companies and how it's costing the RIAA millions, all while alienating their strongest consumer base."

Slashdot Top Deals

Software production is assumed to be a line function, but it is run like a staff function. -- Paul Licker

Working...