Slashdot Mirror

← Back to Domains

Domain: cam.ac.uk

Stories and comments across the archive that link to cam.ac.uk.

Comments · 1,846

  1. Re:Why this is Important by PhilHibbs · · Score: 2 · on EU Studies Linux Migration
    Netproject seem to be embracing TCPA:
    Trusted Computing is set to accelerate the growth of the information economy.
    Opt out - and be in third world of information economies.
    Opt in - and find yourself amongst existing cartels of trust.
    although they do accept that there are criticisms and concerns:
    Ross Anderson is a leading cryptographer and authority on the interaction between security and economics. He has written on the dangers that TCPA holds for privacy, for consumer rights, for competition policy, for innovation and for small business.

    See his list of Frequently Asked Questions at: http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
  2. Re:Typical MS by vidarh · · Score: 2 · on Namibia Says "No Thanks" To Microsoft Donation With Strings

    Cambridge most certainly does pay Microsoft for it under Microsofts Select 4 licensing. See this page for some superficial information about (no prices etc).

  3. Re:Poppycock! by Christopher+Whitt · · Score: 1, Offtopic · on OpenBSD 3.2 Readies For Release, pf Matures

    Of course, the most logical approach is, YYYYMMDD, with significance than follows closer the way we count.

    Not only is this the most logical approach, it's the standard approach. ISO 8601 to be exact. Not only is it logical, but it is also very computer friendly since sorting datestamps that are in this format is easy: an ascending sort is a chronological sort.

  4. Re: cool beans by shogun · · Score: 2 · on Nanotech Paints For Military

    >Just mount a coffee can on your fender, pack it full of shredded aluminum foil and gunpowder, wire your radar detector to set it off, and you can slip through the speed trap in a cloud of chaff.

    I think you might be sues then by the British Air Force for breach of patent/copyright, sound a little similiar to Operation Window.

    yeah i know its the same as contemporary chaff, but I had to find the first instance. ;)

  5. Folding Lag Time by Anonymous Coward · · Score: 1, Insightful · on Folding@Home Reports Success
    --Specifically, the computers predicted that one experimental protein would fold in 6 microseconds, while laboratory observations revealed an actual folding time of 7.5 microseconds.--

    Perhaps the kinetic "experimental" 1.5 usec lag time is what is referred to in this PNAS article by Alan Fersht.

  6. Re:An obvious question from the /. crowd by sh00z · · Score: 1 · on Questions for a Lecture on Microsoft's Palladium?
    If "way back" counts as July, here are some links to the articles I've read:
    "The technology would paste a digital certificate on every byte of data"
    O'Reilly
    (see item 5)
    (google cache of de-generationx)
    Cringely--slightly off-topic, but still interesting
    I do see that Microsoft's FAQ says exactly what you're saying, but I tend to take their statements with a LARGE grain of salt (as yesterday's Astroturf fiasco proved is a reasonable approach).
  7. Who will control Palladium? by bgins · · Score: 2, Interesting · on Questions for a Lecture on Microsoft's Palladium?
    As I understand it from the FAQ mentioned in the original post, Palladium enables 'trusted' computing in the sense that vendors trust the computers to operate according to policies they control. Thus, vendors can wield strong control over their markets and will be encouraged to bring out more copyrighted material without risk of loss of profits. This is Bill Gate's answer to the Software Piracy campaign MS started back in '99 or so.

    The obvious question with this is: What is the control infrastrucure for Palladium? Who controls file revocation lists? Who controls policy enforcement? Who can gain control through the courts? Who can gain control without users' knowledge?

    Specifically, How is storing private RSA keys on an SSC (Security Support Component) different from centralized key escrow management? (Won't the SSC vendor know or at least be able to know the private key?) Also, What are the costs of using blacklists and whitelists?

    Another obvious question, although less technical, is: How this is going to succeed where eBooks have not? Back in 2000, when eBooks were the just coming out, Microsoft predicted that it would be a multibillion dollar industry with rapid growth. Digital copyright protection capability was added to their version with the hope of securing their revenue. How are eBooks doing now? Are there any conclusions that can be drawn from this? Perhaps this is an instructive analogy to extrapolate from.

    Finally, and perhaps most importanly (but least answerable), the two FAQs above paint rather different pictures of Palladium and TCPA. How are we to know what the effects will really be? Do we have to look at the source?

  8. Re:Demand? by m.herbison · · Score: 1 · on Questions for a Lecture on Microsoft's Palladium?
    Looking at the Palladium FAQ, I saw this:

    2. What does TCPA / Palladium do, in ordinary English?

    It provides a computing platform on which you can't tamper with the applications, and where these applications can communicate securely with the vendor. The obvious application is digital rights management (DRM): Disney will be able to sell you DVDs that will decrypt and run on a Palladium platform, but which you won't be able to copy. The music industry will be able to sell you music downloads that you won't be able to swap. They will be able to sell you CDs that you'll only be able to play three times, or only on your birthday. All sorts of new marketing possibilities will open up.

    TCPA / Palladium will also make it much harder for you to run unlicensed software. Pirate software can be detected and deleted remotely. It will also make it easier for people to rent software rather than buying it; and if you stop paying the rent, then not only does the software stop working but so may the files it created. For years, Bill Gates has dreamed of finding a way to make the Chinese pay for software: Palladium could be the answer to his prayer.

    There are many other possibilities. Governments will be able to arrange things so that all Word documents created on civil servants' PCs are `born classified' and can't be leaked electronically to journalists. Auction sites might insist that you use trusted proxy software for bidding, so that you can't bid tactically at the auction. Cheating at computer games could be made more difficult.

    There is a downside too....

    How naive of me -- I thought what they were writing was a list of the drawbacks...ugh.
  9. Re:This actually _is_ funny. by lars_stefan_axelsson · · Score: 5, Interesting · on New "Secure" Xbox Cracked In Under A Week
    I think that the designers of the IBM 4758 [ibm.com] cryptographic coprocessors might disagree. The IBM4732 is supposed to be tampre proof [rutgers.edu].

    And yet, an application on the IBM4732 was hacked a little under a year ago. Granted it wasn't the processor as such, but a very important application that is delivered with the processor. Getting the whole system right is hard.

    If you want more material on why tamper proofing is difficult; Ross Anderson's team at Cambridge is a good resource. (And they have performed a number of nice hacks Markus Kuhn's optical eavesdropping for example).

  10. Re:This actually _is_ funny. by lars_stefan_axelsson · · Score: 5, Interesting · on New "Secure" Xbox Cracked In Under A Week
    I think that the designers of the IBM 4758 [ibm.com] cryptographic coprocessors might disagree. The IBM4732 is supposed to be tampre proof [rutgers.edu].

    And yet, an application on the IBM4732 was hacked a little under a year ago. Granted it wasn't the processor as such, but a very important application that is delivered with the processor. Getting the whole system right is hard.

    If you want more material on why tamper proofing is difficult; Ross Anderson's team at Cambridge is a good resource. (And they have performed a number of nice hacks Markus Kuhn's optical eavesdropping for example).

  11. Re:This actually _is_ funny. by lars_stefan_axelsson · · Score: 5, Interesting · on New "Secure" Xbox Cracked In Under A Week
    I think that the designers of the IBM 4758 [ibm.com] cryptographic coprocessors might disagree. The IBM4732 is supposed to be tampre proof [rutgers.edu].

    And yet, an application on the IBM4732 was hacked a little under a year ago. Granted it wasn't the processor as such, but a very important application that is delivered with the processor. Getting the whole system right is hard.

    If you want more material on why tamper proofing is difficult; Ross Anderson's team at Cambridge is a good resource. (And they have performed a number of nice hacks Markus Kuhn's optical eavesdropping for example).

  12. Continuous update by Zeinfeld · · Score: 5, Interesting · on Still More on News Corp. Hacking Charges
    An interesting feature of the satelite smartcard scene is that the protection schemes are designed with the knowledge they can be craked.

    Ultimately no security scheme based on commodity hardware is secure against a determined attack. Even the clipper chip was broken. If the adversary has a scanning electron microscope available they are going to be able to reverse engineer the chip. Ross Andersson did a paper on this a while back.

    The strategy the satellite companies use today is economic rather than purely technical. What they do is to design smart cards which are subject to progressive security flaws. They then send out different variations on the smart card to different customers.

    The trick is that the pirate does not know which of the flaws matter and which do not. So if the pirate clones a particular card perfectly the satellite company can respond cheaply and effectively by just replacing the small number of cards that have been compromised.

    If the pirate makes a more general attack the satelite co looks for any small difference between the cloned card and the genuine cards and programs a deactivation code to take advantage.

    Most cloned cards are not perfect since the pirates are in competition with each other. It is better to get a cloned card out in 3 weeks than to wait a n extra couple of months and allow a competitor to steal the market.

    The satelite cos generally wait until the pirates have sold a significant number of cards before sending out the deactivation codes. This discredits the pirates with more customers. If the customers learn that using a pirate card ends up costing them more than being honest in addition to being inconvenient they are more likely to turn honest. Another trick is to disable the cards right before big events.

  13. Continuous update by Zeinfeld · · Score: 5, Interesting · on Still More on News Corp. Hacking Charges
    An interesting feature of the satelite smartcard scene is that the protection schemes are designed with the knowledge they can be craked.

    Ultimately no security scheme based on commodity hardware is secure against a determined attack. Even the clipper chip was broken. If the adversary has a scanning electron microscope available they are going to be able to reverse engineer the chip. Ross Andersson did a paper on this a while back.

    The strategy the satellite companies use today is economic rather than purely technical. What they do is to design smart cards which are subject to progressive security flaws. They then send out different variations on the smart card to different customers.

    The trick is that the pirate does not know which of the flaws matter and which do not. So if the pirate clones a particular card perfectly the satellite company can respond cheaply and effectively by just replacing the small number of cards that have been compromised.

    If the pirate makes a more general attack the satelite co looks for any small difference between the cloned card and the genuine cards and programs a deactivation code to take advantage.

    Most cloned cards are not perfect since the pirates are in competition with each other. It is better to get a cloned card out in 3 weeks than to wait a n extra couple of months and allow a competitor to steal the market.

    The satelite cos generally wait until the pirates have sold a significant number of cards before sending out the deactivation codes. This discredits the pirates with more customers. If the customers learn that using a pirate card ends up costing them more than being honest in addition to being inconvenient they are more likely to turn honest. Another trick is to disable the cards right before big events.

  14. Re:This was posted six months ago, by jonasj · · Score: 1 · on The Rise and Fall of the Geek

    A good time to start using ISO time.

  15. Background on Fortran by tibbetts · · Score: 5, Informative · on Fortran 2000 Committee Draft

    For those of us under 50, here's some history of the granddaddy of all high-level programming languages.

    IIRC, my former graduate advisor and professor was on the team that wrote a very early Fortran compilers at MIT in the late 50s, written entirely on punch cards. We've come a long way in ~50 years.

  16. FIPS 140 - whats good and bad? by seaan · · Score: 2 · on Questioning Security Certifications

    From my experience, the FIPS 140 certificate does a good job of ensuring that products live-up to their formal design specifications. The obvious question is how good were the design specifications? This is where things get interesting. To over generalize, I think FIPS 140 does a good on tamper-resistant (and respondent) hardware design, and a poor job on logical security.

    A lot of the FIPS philosophy came out of the military, and the testing labs impressed me with the breadth of their physical attacks. On the other hand, the military usually has very simple logical security requirements for a crypto-box. It should be inert until authorized users properly activate it, and at that point it can perform sensitive actions. Commercial cryptography designs by contrast, usually has a set of functions that needs to be generally available. They also have a much smaller set of functions that need authorized users to control.

    When we put our product through the immediate predecessor to FIPS 140-1 certification, we were the first commercial product and ended-up breaking a fair-amount of new ground (somewhat painfully as you might imagine). What we had to show was that the cryptographic commands that were available to non-privileged users were safe - because of the logical security design. Even early FIPS 140-1 processes did not really deal with these "always-on" functions very well.

    Although it improved, especially with the 140-2 modifications, logical security is still the real weak point. Michael Bond's well publicized attacks on the FIP 140-1 level 4 certified IBM 4758 security module were all aimed at the "logical security" level. My favorite example of insecure by design is the PKCS #11 security module when it is used for server security.

    The Cryptoki (PKCS #11) interface was designed for security tokens, and basically works a lot like the military devices. The token (smartcard, whatever) would be plugged into the client device, where it would remain inert until activated by the user password. Actually a pretty good design when used this way.

    The problem is when the same design is used for a server, which is unfortunately common since several PKI vendors standardized on using PKCS #11 security modules. PKCS #11 authorization levels are all messed-up for server use. There is no concept of "always-on" commands, or multiple levels of authorization. That means that any entity (server application) that wants to access the security-subsystem must be an authorized user.

    The result is that the clear password that enables the PKCS# 11 modules has to be put into the server application. Because of that clear password an attacker no longer has to break into the PKCS #11 box or steal/forge authorized user's identities. They can gain authorized user privileges merely by monitoring the communication lines between the application and box, or by analyzing the object code of the application!

    You will find a number of FIPS 140 certified PKCS #11 modules, which is actually no surprise given how well PKCS #11 matches the military origins of the FIPS 140. This is a classic example of a certified subsystem that is quite secure for some uses (human insertion of a token and entry of password), but it quite insecure for others (server applications storing and using clear passwords). All the FIPS certification does in the case of PKCS #11 is tell you that the vendor has followed their design, and not if it will provide logical security in your system!

  17. There's a good reason the Chinese want this... by JudasBlue · · Score: 1 · on China Develops Their Own CPU: The "Dragon Chip"
    The following is from a FAQ about Palladium:
    "TCPA / Palladium will also make it much harder for you to run unlicensed software. Pirate software can be detected and deleted remotely."

    Now think about this in terms of national security for a second. If you have processor embeded tech that allows corporations to see things in your systems, how secure do you think your systems are going to be?

    Moving to an OS and chip combination that allows you to keep your information secure is going to be a big priority.

  18. Unsurprising by Fluffy+the+Cat · · Score: 3, Interesting · on Antibiotic Resistant Staph Infections

    The number of bacteria on the planet is unimaginably huge. Bacteria are capable of passing genes between each other horizontally. As a result, you can effectively treat the entire bacterial population of the planet as a single gene pool. Given enough time, any beneficial mutation will pass from one end of the population to the other.

    Now, this is obviously a problem in terms of antibiotics. Many antibiotics are still generated from natural sources, and some fairly harmless bacterial species has probably developed immunity to that (by virtue of happening to live in the soil around the ferns that secrete it, for example). The genes providing that immunity can pass to pretty much ever other bacterial species on the planet. This isn't a rapid process, but it will be sped up by imposing additional selection pressure - for instance, treating bacteria with that antibiotic.

    Overuse or inappropriate use of antibiotics isn't really the trigger here. Imposing any degree of selection pressure will result in the same thing happening - it's only a matter of timing. More careful use of antibiotics may give us a few hundred years more if we're lucky, ten years more if we're not. The point to remember is that no matter how clever your antibiotic, there will be a gene in some bacterium somewhere that provides immunity to it. And, if you wait long enough, that will end up in the bacteria you're trying to kill.

    It's not an intractable problem. There's likely to (somewhere) be an enzyme that will digest your antibiotic, but if you develop something that degrades that enzyme you're back in business. The chances of a random bacterium having both the resistance and an unrelated gene that protects the resistance mechanism is the square root of the probability of it having the resistance alone (probably less - having the resistance is likely to have proven useful in nature, and so will be more popular. The probability of having both genes will therefore be corespondingly less), which gives us a fighting chance. New techniques in drug development are likely to mean that we can design new drgs that can defeat any resistance mechanism that turns up.

    Remember though, antibiotics have only been around for a hundred years or so. Humanity survived before then. Antibiotics increase average life expectency, but they're not required for continued human survival.

    My final year dissertation was on this topic. You can find a copy at www-jcsu.jesus.cam.ac.uk/~mjg59/resistance.pdf .

  19. Re:You're missing the critical part by adb · · Score: 1 · on AMD Opteron to support Palladium

    RTFFAQ. (And who said the alien clones had to be super-intelligent? They'd be noticed, especially among Republicans.)

  20. They're Already Doing It by Foresto · · Score: 2, Informative · on RIAA Seeks Summary Judgement Against P2P Services

    "With this logic, PC's should be banned as they can copy music"

    They're already trying to do something like that, but instead of banning PCs and services, they want to turn them into devices that they can control. For example, check out Palladium. Last time I checked, both AMD and Intel had bought in to this.
  21. Re:Try being a private pilot these days by oliphaunt · · Score: 2 · on How Has Post-9/11 Legislation Affected You?
    Imagine owning property but being subject to a security check before you were allowed to go out to it.


    That's coming too. Just hang on a bit, and the FBI will catch up with the MPAA for sure.

    Your problem is these concepts of "rights," "ownership," and "property." Who are you to decide what you own, or what rights you have? That's a job that you had better leave to the government.
  22. GPL implications by Razzy · · Score: 1 · on Intel to Build DRM into Next-Generation CPUs

    Anyone else notice point 18 of Ross Anderson's FAQ? It notes that TCPA and Palladium can be used to circumvent the GPL. TCPA enhanced version of open source software (i.e. TCPA GNU/Linux) would have to be certified by the TCPA consortium. Such certification would cost a substantial amount of money, which means businesses could do it but individuals couldn't. This means that corporations would be able to steal open source code without breaking copyright law. The source would still be free, but that would mean nothing because any modified version of the source would require revalidation, making it somewhat worthless in a practical context. Microsoft could even open-source windows media player with absolutely no fear because only certified systems would be allowed to access the content necessary to make wmp useful.

    This isn't only scary because it is a disincentive for open source development. Think of its use as a smokescreen. We all yell "uncompetative business practices" because Microsoft and Intel have a stranglehold on the computing market maintained by DRM and "trusted" computing, but they say, "what are you talking about, all of our software is open source." Also, note that it is going to be hard to brand this uncompetative in any case because TCPA is an open standard maintained by a consortium, which might more aptly be called a cartel (see Anderson's point 20).

    The GPL was created with the assumption that open source meant open computing. How do we protect ourselves in an environment where protecting the source code may not be enough?

  23. No, it's not already here by Anonymous Coward · · Score: 0 · on Intel to Build DRM into Next-Generation CPUs

    At the moment you can get round this nonsense - just load the page with javascript disabled, and then view source. (or wget --user-agent="Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)" )

    With a TCPA PC you will either be unable to decrypt the page (in non-trusted mode) or be running a "trusted" browser that really enforces these restrictions (they'll probably force you to view the popups too. yech!)

    As for what "trusted" means, see Questions 24 and 25 of Ross Anderson's FAQ

  24. Not Microsoft's Initiative by Anonymous Coward · · Score: 0 · on Intel to Build DRM into Next-Generation CPUs

    Would people *please* stop thinking of this hardware DRM business as originiating with Microsoft's Palladium. It didn't.

    Everybody PLEASE read the TCPA/Palladium FAQ which was posted here on slashdot a while ago.

    The initiative to develop harware based DRM in PC CPU's came from Intel, not Microsoft. Palladium is Microsoft's support for Intel's (or rather the TCPA's) DRM initiative, not the other way around.

  25. The theft of our freedoms by frank_slashdot · · Score: 2, Informative · on Palladium, 'Trusted PCs' in the News


    The worst of all is that people will be forced to use Palladium or TCPA machines, when laws like CBDTPA (the former SSSCA) will be passed.

    Thus, sooner or later, the right to share will be outlawed, and people will no longer be able to "turn DRM off".

    When no TCPA-free or Palladium-free hardware will be available and the ISPs will only allow TCPA machines to be connected to the Internet, there will be no alternative.

    The worst of all, most of the people are totally unaware that many of their freedoms are about to be stolen.

    For an introduction see:

    http://action.eff.org/tinseltown/

    http://www.eff.org/IP/SSSCA_CBDTPA/

    TCPA / Palladium Frequently Asked Questions

    http://www.cl.cam.ac.uk/users/rja14/tcpa-faq.html

    "The Right to Read" by Richard M. Stallman.

    http://www.fsf.org/philosophy/right-to-read.html

    (The important thing about this story is that it was written before the DMCA was even proposed!)

    "What's Wrong With Copy Protection" by John Gilmore.

    http://cryptome.org/jg-wwwcp.htm


  26. Re:Seth Schoen's Palladium Summary by Andersj · · Score: 1 · on Palladium, 'Trusted PCs' in the News

    Another very good summary and information source is Ross Anderson's TCPA/Palladium FAQ

  27. Re:Get a fucking telescope by Mr_Dyqik · · Score: 2 · on First Commercial Moon Mission Approved

    Other challenges are combining the light from each mirror in phase to within about a tenth of a wavelength (50 nm say for light). Then you would have a telescope that could _only_ see details 1 milli arc second across. You'd get no signal from details 2 milli arc second across. To make an image you have to scan the distance between the mirrors, and you have to scan the whole system in 2-d to build a 2-d image. You get let the earth's rotation do one of those things for you if you wish. The computer reconstruction time to build the image would probably stop any of the hoax nutters believing you. COAST does this

  28. Re:It was to be expected... by Schnapple · · Score: 2 · on Judge Kills Napster Sale Over Conflict of Interest
    They stole the Palladium first, because that was what protected Troy.
    And now we have Microsoft's Palladium to deal with. Ironic, no?
  29. The beginning of the new CBDTPA / TCPA / Palladium by Anonymous Coward · · Score: 0 · on Microsoft/HP to Market Crippled Entertainment PCs


    The era "free as in freedom" is over. The new CBDTPA / TCPA / Palladium era is about to begin.

    Ross Anderson on TCPA
    http://cryptome.org/tcpa-rja2.htm

    TCPA / Palladium Frequently Asked Questions
    http://www.cl.cam.ac.uk/users/rja14/tcpa-faq.html

    Microsoft Digital Rights Management Operating System - US Patent No. 6,330,670
    http://cryptome.org/ms-drm-os.htm

    Microsfot Digital Rights Management Operating System - US Patent No. 6,327,652
    http://cryptome.org/ms-drm-os2.htm

    Hollings' CBDTPA = TCPA Enablement Act
    http://cryptome.org/tcpa-fritz.htm

    Some very interesting quotes from the above documents:

    "During my investigations into TCPA, I learned that HP has started a development program to produce a TCPA-compliant version of GNU/linux. I couldn't figure out how they planned to make money out of this. On Thursday, at the Open Source Software Economics conference, I figured out how they might.

    Making a TCPA-compliant version of GNU/linux (or Apache, or whatever) will mean tidying up the code and removing whatever features conflict with the TCPA security policy. The company will then submit the pruned code to an evaluator, together with a mass of documentation for the work that's been done, including a whole lot of analyses showing, for example, that you can't get root by a buffer overflow.

    The business model, I believe, is this. HP will not dispute that the resulting `pruned code' is covered by the GPL. You will be able to download it, compile it, check it against the binary, and do what you like with it. However, to make it into TCPA-linux, to run it on a TCPA-enabled machine in privileged mode, you need more than the code. You need a valid signature on the binary, plus a cert to use the TCPA PKI. That will cost you money (if not at first, then eventually).

    Anyone will be free to make modifications to the pruned code, but in the absence of a signature the resulting O/S won't enable users to access TCPA features. It will of course be open to competitors to try to re-do the evaluation effort for enhanced versions of the pruned code, but that will cost money; six figures at least. There will likely be little motive for commercial competitors to do it, as HP will have the first mover advantages and will be able to undercut them on price. There will also be little incentive for philanthropists to do it, as the resulting product would not really be a GPL version of a TCPA operating system, but a proprietary operating system that the philanthropist could give away free. (There are still issues about who would pay for use of the PKI that hands out user certs.) The need to go through evaluation with each change is completely incompatible with the business model of free and open source software."


    So make sure you tell everyone you know to prepare for the future.

    The Stuckist Net
    http://www.theregister.co.uk/content/6/26740.html
    http://www.theregister.co.uk/content/35/26796.html


  30. Just use Dasher by charlie763 · · Score: 1 · on Images and Screen Shots of Zaurus SL-A300

    Even though there is no keyboard, text input shouldn't be all that hard. Remember the article about typing with you eyes a few weeks ago? A program called Dasher is the fastest way to input text aside from a keyboard.

  31. Re:One word : by lamp77 · · Score: 1 · on Hotmail: Not Safe For Work?

    well, maybe we should all use dasher now, to get around keylogging.

    dasher+hushmail == very good.

  32. Re:Duplicity by Anonymous Coward · · Score: -1, Troll · on Sun Includes Microsoft-Like Automatic Updates Clause

    Fuck you cunt.
    http://hal.trinhall.cam.ac.uk/~nrs27

    Try making your cunt signature a link. I hate that shit. Fucking cunt.

    Your site is fag gay.

    Neil you are a fag.

    Your PGP key isnt there because you cant get it to work with Outlook.

    Your house looks like a pigsty shithole typical of fat people who get no sex.

    Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

    You have broken links, prick.

    W3C validator found errors in your shit site.
    Genrally you make me sick

    Line 9, column 42: . . ^Error: unknown entity "apos" . .
    Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
    Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
    Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 34, column 18: . that went wrong
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 36, column 13: . and pieces
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 37, column 50: . . ull example of MS Word applying itself to html)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 38, column 50: . . ct areas, using an abbreviation for the course.
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 30: . Slashdot
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 48: . Slashdot
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 39: . The Register
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 60: . The Register
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 37: . The Inquirer
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 58: . The Inquirer
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 36: . BBC News
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 53: . BBC News
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 47, column 14: . Branch)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 18: . Peter
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 33: . Peter
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 42: . Chris
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 56: . Chris
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 43: . John
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 56: . John
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 43: . Joe
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 56: . Joe
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 43: . Matt
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 56: . Matt
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 43: . Stu
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 54: . Stu
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 42: . Dr. Simon Moore
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 66: . Dr. Simon Moore
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
    Line 65, column 3: .
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

  33. Re:Duplicity by Anonymous Coward · · Score: -1, Troll · on Sun Includes Microsoft-Like Automatic Updates Clause

    Fuck you cunt.
    http://hal.trinhall.cam.ac.uk/~nrs27

    Try making your cunt signature a link. I hate that shit. Fucking cunt.

    Your site is fag gay.

    Neil you are a fag.

    Your PGP key isnt there because you cant get it to work with Outlook.

    Your house looks like a pigsty shithole typical of fat people who get no sex.

    Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

    You have broken links, prick.

    W3C validator found errors in your shit site.
    Genrally you make me sick

    Line 9, column 42: . . ^Error: unknown entity "apos" . .
    Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
    Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
    Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 34, column 18: . that went wrong
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 36, column 13: . and pieces
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 37, column 50: . . ull example of MS Word applying itself to html)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 38, column 50: . . ct areas, using an abbreviation for the course.
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 30: . Slashdot
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 48: . Slashdot
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 39: . The Register
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 60: . The Register
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 37: . The Inquirer
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 58: . The Inquirer
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 36: . BBC News
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 53: . BBC News
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 47, column 14: . Branch)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 18: . Peter
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 33: . Peter
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 42: . Chris
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 56: . Chris
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 43: . John
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 56: . John
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 43: . Joe
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 56: . Joe
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 43: . Matt
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 56: . Matt
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 43: . Stu
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 54: . Stu
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 42: . Dr. Simon Moore
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 66: . Dr. Simon Moore
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
    Line 65, column 3: .
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

  34. Re:Duplicity by Anonymous Coward · · Score: -1, Troll · on Sun Includes Microsoft-Like Automatic Updates Clause

    Fuck you cunt.
    http://hal.trinhall.cam.ac.uk/~nrs27

    Try making your cunt signature a link. I hate that shit. Fucking cunt.

    Your site is fag gay.

    Neil you are a fag.

    Your PGP key isnt there because you cant get it to work with Outlook.

    Your house looks like a pigsty shithole typical of fat people who get no sex.

    Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

    You have broken links, prick.

    W3C validator found errors in your shit site.
    Genrally you make me sick

    Line 9, column 42: . . ^Error: unknown entity "apos" . .
    Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
    Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
    Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 34, column 18: . that went wrong
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 36, column 13: . and pieces
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 37, column 50: . . ull example of MS Word applying itself to html)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 38, column 50: . . ct areas, using an abbreviation for the course.
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 30: . Slashdot
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 48: . Slashdot
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 39: . The Register
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 60: . The Register
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 37: . The Inquirer
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 58: . The Inquirer
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 36: . BBC News
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 53: . BBC News
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 47, column 14: . Branch)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 18: . Peter
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 33: . Peter
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 42: . Chris
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 56: . Chris
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 43: . John
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 56: . John
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 43: . Joe
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 56: . Joe
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 43: . Matt
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 56: . Matt
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 43: . Stu
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 54: . Stu
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 42: . Dr. Simon Moore
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 66: . Dr. Simon Moore
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
    Line 65, column 3: .
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

  35. Re:Duplicity by Anonymous Coward · · Score: -1, Troll · on Sun Includes Microsoft-Like Automatic Updates Clause

    Fuck you cunt.
    http://hal.trinhall.cam.ac.uk/~nrs27

    Try making your cunt signature a link. I hate that shit. Fucking cunt.

    Your site is fag gay.

    Neil you are a fag.

    Your PGP key isnt there because you cant get it to work with Outlook.

    Your house looks like a pigsty shithole typical of fat people who get no sex.

    Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

    You have broken links, prick.

    W3C validator found errors in your shit site.
    Genrally you make me sick

    Line 9, column 42: . . ^Error: unknown entity "apos" . .
    Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
    Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
    Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 34, column 18: . that went wrong
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 36, column 13: . and pieces
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 37, column 50: . . ull example of MS Word applying itself to html)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 38, column 50: . . ct areas, using an abbreviation for the course.
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 30: . Slashdot
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 48: . Slashdot
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 39: . The Register
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 60: . The Register
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 37: . The Inquirer
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 58: . The Inquirer
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 36: . BBC News
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 53: . BBC News
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 47, column 14: . Branch)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 18: . Peter
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 33: . Peter
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 42: . Chris
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 56: . Chris
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 43: . John
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 56: . John
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 43: . Joe
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 56: . Joe
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 43: . Matt
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 56: . Matt
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 43: . Stu
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 54: . Stu
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 42: . Dr. Simon Moore
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 66: . Dr. Simon Moore
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
    Line 65, column 3: .
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

  36. Re:Duplicity by Anonymous Coward · · Score: -1, Troll · on Sun Includes Microsoft-Like Automatic Updates Clause

    Fuck you cunt.
    http://hal.trinhall.cam.ac.uk/~nrs27

    Try making your cunt signature a link. I hate that shit. Fucking cunt.

    Your site is fag gay.

    Neil you are a fag.

    Your PGP key isnt there because you cant get it to work with Outlook.

    Your house looks like a pigsty shithole typical of fat people who get no sex.

    Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

    You have broken links, prick.

    W3C validator found errors in your shit site.
    Genrally you make me sick

    Line 9, column 42: . . ^Error: unknown entity "apos" . .
    Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
    Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
    Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 34, column 18: . that went wrong
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 36, column 13: . and pieces
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 37, column 50: . . ull example of MS Word applying itself to html)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 38, column 50: . . ct areas, using an abbreviation for the course.
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 30: . Slashdot
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 48: . Slashdot
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 39: . The Register
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 60: . The Register
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 37: . The Inquirer
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 58: . The Inquirer
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 36: . BBC News
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 53: . BBC News
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 47, column 14: . Branch)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 18: . Peter
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 33: . Peter
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 42: . Chris
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 56: . Chris
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 43: . John
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 56: . John
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 43: . Joe
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 56: . Joe
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 43: . Matt
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 56: . Matt
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 43: . Stu
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 54: . Stu
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 42: . Dr. Simon Moore
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 66: . Dr. Simon Moore
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
    Line 65, column 3: .
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

  37. Re:Duplicity by Anonymous Coward · · Score: -1, Troll · on Sun Includes Microsoft-Like Automatic Updates Clause

    Fuck you cunt.
    http://hal.trinhall.cam.ac.uk/~nrs27

    Try making your cunt signature a link. I hate that shit. Fucking cunt.

    Your site is fag gay.

    Neil you are a fag.

    Your PGP key isnt there because you cant get it to work with Outlook.

    Your house looks like a pigsty shithole typical of fat people who get no sex.

    Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

    You have broken links, prick.

    W3C validator found errors in your shit site.
    Genrally you make me sick

    Line 9, column 42: . . ^Error: unknown entity "apos" . .
    Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
    Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
    Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 34, column 18: . that went wrong
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 36, column 13: . and pieces
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 37, column 50: . . ull example of MS Word applying itself to html)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 38, column 50: . . ct areas, using an abbreviation for the course.
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 30: . Slashdot
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 48: . Slashdot
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 39: . The Register
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 60: . The Register
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 37: . The Inquirer
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 58: . The Inquirer
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 36: . BBC News
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 53: . BBC News
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 47, column 14: . Branch)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 18: . Peter
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 33: . Peter
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 42: . Chris
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 56: . Chris
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 43: . John
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 56: . John
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 43: . Joe
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 56: . Joe
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 43: . Matt
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 56: . Matt
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 43: . Stu
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 54: . Stu
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 42: . Dr. Simon Moore
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 66: . Dr. Simon Moore
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
    Line 65, column 3: .
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

  38. Re:Duplicity by Anonymous Coward · · Score: -1, Troll · on Sun Includes Microsoft-Like Automatic Updates Clause

    Fuck you cunt.
    http://hal.trinhall.cam.ac.uk/~nrs27

    Try making your cunt signature a link. I hate that shit. Fucking cunt.

    Your site is fag gay.

    Neil you are a fag.

    Your PGP key isnt there because you cant get it to work with Outlook.

    Your house looks like a pigsty shithole typical of fat people who get no sex.

    Helen Butler looks like she has chunky brown vaginal discharges. You and your friends look like fags.

    You have broken links, prick.

    W3C validator found errors in your shit site.
    Genrally you make me sick

    Line 9, column 42: . . ^Error: unknown entity "apos" . .
    Line 11, column 13: . . ^Error: there is no attribute "ALINK" for this element (in this HTML version) . .
    Line 20, column 3: . You can find my PGP key here (when I put it . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 20, column 35: . . find my PGP key here (when I put it . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 20, column 35: . . GP key here (when I put it up). . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 0: . The gallery contains a large selecti . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 31: . . The gallery contains a lar . . ^Error: there is no attribute "TARGET" for this element (in this HTML version) . .
    Line 27, column 33: . . The gallery contains a lar . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 35: . . ="./gallery" target="">gallery contains a large selectio . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 27, column 50: . . stuff. Also see the second gallery, . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 27, column 50: . . second gallery, which contains stu . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 33, column 30: . . mouse.v - a example for c . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 33, column 35: . . ef="mouse.v" target="">mouse.v - a example for compsci t . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 34, column 18: . that went wrong
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . a href="./java/java.html" target="">Java - collection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 35, column 35: . . java/java.html" target="">Java - collection of java bits . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 36, column 13: . and pieces
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 27: . . old - the site that used to . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 37, column 35: . . old - the site that used to b . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 37, column 50: . . ull example of MS Word applying itself to html)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 34: . . Work - A selection of . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 38, column 35: . . ="./work" target="_blank">Work - A selection of bits of . . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 38, column 50: . . ct areas, using an abbreviation for the course.
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 30: . Slashdot
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 41, column 48: . Slashdot
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 39: . The Register
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 42, column 60: . The Register
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 37: . The Inquirer
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 43, column 58: . The Inquirer
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 36: . BBC News
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 44, column 53: . BBC News
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 35: . . ttp://www.srcf.ucam.org/assassins/"> The Cambridge Assasins . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 45, column 50: . . g/assassins/"> The Cambridge Assasins Guild
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 46, column 35: . . http://www.aaib.dtlr.gov.uk/index/"> AAIB (Air Accidents Inv . . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 47, column 14: . Branch)
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 18: . Peter
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 51, column 33: . Peter
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 42: . Chris
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 52, column 56: . Chris
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 43: . John
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 53, column 56: . John
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 43: . Joe
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 54, column 56: . Joe
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 43: . Matt
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 55, column 56: . Matt
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 43: . Stu
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 56, column 54: . Stu
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 42: . Dr. Simon Moore
    . ^Error: element "A" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 57, column 66: . Dr. Simon Moore
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 61, column 0: . A small set of instructions / scripts to get sound working in GnomeICU . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . .
    Line 62, column 9: . Small(Small( . ^Error: end tag for element "A" which is not open; try removing the end tag or check for improper nesting of elements . .
    Line 65, column 3: .
    . ^Error: element "BR" not allowed here; possible cause is an in
    Line element containing a block-level element . .
    Line 67, column 0: . Copyright 2001 N. Smith (nrs27@nospam.cam.ac.uk) Last modified 10th . ^Error: text is not allowed here; try wrapping the text in a more descriptive container . . .

  39. Re:"On the internet" doesn't quite cover it by symbolic · · Score: 3, Interesting · on Network Associates Buys "Better Carnivore"

    Check this out. This FAQ regarding Palladium, in addition to the endless quest to engage in unreasonable searches (a al Carnivore and its brethren), are going to make for some interesting times. It gives rise to what I think is an important question - what happens when one or more private entities act in consort with a government to subvert the premises on which a society is founded?

  40. Re:Our issue by xiox · · Score: 2 · on Can We Finally Ditch Exchange?

    The webmail service the University of Cambridge uses is pretty good, but it doesn't seem to have any identification. Maybe it was developed in-house or is a highly customised code. Perhaps one of the guys there would let you know what they're using (look around for contacts).

    See this

  41. Stephen Hawking by stixman · · Score: 2, Interesting · on Type With Your Eyes

    Did anybody else think immediately about Stephen Hawking upon seeing this? I searched the site, and it says in the history that he was originally one of the mein targets for the project. Anything that can possibly help him to communicate faster would be wonderful, as well as for all other disabled people. Nice work so far!

  42. Re:Project homepage at sourceforge by Anonymous Coward · · Score: 0 · on Crush/BRiX: An Experimental Language/OS Pair
    Did anyone read the info page?
    BRiX, unlike other modern operating systems, does not use hardware to isolate and protect applications from each other. Instead, it uses a single address space and relies on a safe-language to generate code that will not access memory for which it does not own. This language also handles many checks at compile-time that would be performed at run-time in other operating systems. ... bounds checks can be disabled for stable critical system components. Only untrusted user code is slowed down by the bounds checks.
    While I congradualate Mr. Huntsman on his attempted elevation of computer security now that Dijkstra is long gone, I must take the above claims with extreme skeptism. Such double-talk as "untrusted user code" reminds one of none other than Microsoft Palladium Trusted Computing Platform Alliance. The truth is, designating certain combinations of codes trusted will only provide to dilute computer security further moving us back to the stone age. Trusting kernel code to be flawless and lacking buffer overflows so common on all stack-based architectures will only open the Internet up to larger magnitudes of terrorism. GOBBLES, anyone?
  43. Re:Context! Purpose! by fm6 · · Score: 2 · on Any rxvt-Sized Unicode-Aware Terminal Emulators?
    Actually, the Romans didn't invent most of our glyphs. The Romans didn't have J, U, W, Y or Z, and only used K when writing Greek words. And they didn't have lower-case letters or punctuation. All invented later.

    But I digress. You seem to be assuming that "Unicode support" is this magic thing you can add to any program and suddenly support every Unicode character. In fact, no program directly supports the complete Unicode character set -- Unicode was never meant to be used that way. Instead you support an "encoding" that gives you access to a manageable subset of Unicode.

    The most widely-used encoding is UTF-16, which supports a 2^16-character subset of Unicode. Most major programming languages support both ASCII and UTF-16. Some (notably Java and Visual Basic) support UTF-16 instead of ASCII. Unfortunately, the documentation for these languages usually refers to their their "wide" characters as "unicode" characters, as if Unicode were just a 16-bit "universal" character set. In fact, there are important Unicode-supported characters that are not in UTF-16.

    There's also UTF-8, a variable-width encoding that's backward-compatible with ASCII. I believe GCC already supports UTF-8, and could probably be made to support UTF-16, as most C compilers aready do. And since GCC is written in GCC, you could probably allow kernel programmers to use these extended character sets in their source code. But it's a tricky thing to do, and it's difficult to see the benefit.

    I hate the term "politically correct", but maybe it applies here. You seem to feel that any software that isn't character-set-agnostic is unfair to non-Western users. Putting such an assumption ahead of issues of reliability and security is a very poor kind of prioritizing.

  44. Re:TCPA / Palladium FAQ v1.0 by pmz · · Score: 3, Informative · on Schneier Analyzes Palladium

    Part of the answer for question 22 in Ross' FAQ is even more disturbing:

    "When I asked [the Microsoft Research speaker] whether this meant getting rid of linux he replied that linux users would have to be made to use content screening."

    Currently, there is a "digital divide" between those who have computers and Internet access and those who don't. Palladium raises the bar to divide those who have Palladium and those who don't. This scares the shit out of me (not literally, now, put probably so in a few years).

    If power over people is founded in controlling information, then....

  45. TCPA / Palladium FAQ v1.0 by Camillo · · Score: 4, Informative · on Schneier Analyzes Palladium
    Bruce also refers to Ross Anderson's TCPA/Palladium FAQ, which is well worth a read. Of particular /. interest is question 18, cryptically titled "Ugh. What else?":

    "TCPA will undermine the General Public License (GPL), under which many free and open source software products are distributed." "You will still be free to make modifications to the modified code, but you won't be able to get a certificate that gets you into the TCPA system."

    A lot of background information can also be found from Ross' page about Economics and Security.

    You should ask yourself the question "if a computer can run code in a protected environment, whose code would you be willing to let into the computer?" Once it's there, it is protected - even from you.

  46. TCPA / Palladium FAQ v1.0 by Camillo · · Score: 4, Informative · on Schneier Analyzes Palladium
    Bruce also refers to Ross Anderson's TCPA/Palladium FAQ, which is well worth a read. Of particular /. interest is question 18, cryptically titled "Ugh. What else?":

    "TCPA will undermine the General Public License (GPL), under which many free and open source software products are distributed." "You will still be free to make modifications to the modified code, but you won't be able to get a certificate that gets you into the TCPA system."

    A lot of background information can also be found from Ross' page about Economics and Security.

    You should ask yourself the question "if a computer can run code in a protected environment, whose code would you be willing to let into the computer?" Once it's there, it is protected - even from you.

  47. UTF-8 is The Way (TM) by joib · · Score: 2 · on Linux Continues March On China

    UTF-8 is somewhat ascii compatible, and an efficient coding for mostly ascii data. Looks like the unix world, ietf protocols etc. are moving in this direction. For more info check out
    UTF-8 and Unicode FAQ for Unix/Linux.

  48. Read Ross Anderson's work by Camillo · · Score: 5, Informative · on Distributed Security
    Bruce's "enlightenment" is of course a good thing, and he is brilliant in his way of presenting security issues for the masses. However, security engineering is far from a new field, and many of the principles are well established.

    Take a look at Ross Anderson's home page, read a few of his classics like "Why Cryptosystems Fail", "Programming Satan's Computer" and "The Cocain Auction Protocol".

    Ross' book "Security Engineering - A Guide to Building Dependable Distributed Systems" should be mandatory reading for anyone who writes code for networked computers - no matter what kind of computers.

    I feel that one of the biggest threats to Internet security today is the inability to learn from history. That is, after all, at the core of the engineering arts and sciences.

  49. Automatic dial announcement devices illegal in USA by yerricde · · Score: 2, Interesting · on [Junk]Fax.com Fined $5.4 Million

    It's worth noting that in my state (Arizona), [spamming telephones using automatic dial announcement devices] is illegal.

    It's also illegal in the United States for anyone involved in interstate commerce. It was made illegal as part of the same junk fax law (47 USC 227), which I refuse to call the TCPA because of the Palladium implications.

  50. Ability to speak by Anonymous Coward · · Score: 0 · on A Humanitarian Engineering Problem
    As I recall, Mr. Hawkings had a system that would allow him to very slowly link letters together into words. If you are interested or perhaps a few people here can help you can give your friend the power of speech.

    Take the Dasher interface mentioned a while ago and link it to a text to speech engine(festival) and give your friend a fairly quick and easy way to talk.

    The Duck

    Dasher http://www.inference.phy.cam.ac.uk/dasher/

    Festival http://www.cstr.ed.ac.uk/projects/festival/