Slashdot Mirror


Tim Berners-Lee on the Web

notmyopinion writes "In a wide-ranging interview with the British Computer Society, Sir Tim Berners-Lee criticizes software patents, speaks out on US and ICANN control of the Internet, proposes browser security changes, and says he got domain names backwards in web addresses all those years ago."

22 of 224 comments (clear)

  1. Finally! by Anonymous Coward · · Score: 5, Funny

    It's about time he got on the web. I mean, it's like 15 years old. Everyone is on it these days.

  2. Sir Tim by XanC · · Score: 4, Insightful
    "Sir Tim"

    I found this amusing, along the lines of "there are those who call me.... Tim."

    Seriously though, I thought he had some great things to say about professionalism in IT. We all need to absorb and remember this:

    Customers need to be given control of their own data - not being tied into a certain manufacturer so that when there are problems they are always obliged to go back to them. IT professionals have a responsibility to understand the use of standards and the importance of making Web applications that work with any kind of device.
  3. Looking back... by m85476585 · · Score: 4, Funny

    "Looking back on 15 years or so of development of the Web is there anything you would do differently given the chance?

    I would have skipped on the double slash - there's no need for it. Also I would have put the domain name in the reverse order - in order of size so, for example, the BCS address would read: http://uk.org.bcs/members. The last two terms of this example could both be servers if necessary."


    He could do anything differently and he would drop a slash?

    1. Re:Looking back... by xoboots · · Score: 4, Interesting

      I say it is a good thing that he just followed DNS naming and didn't have 15 years to think of a "better" way -- because the DNS name IS the better way since it saves a lot of useless reordering.

    2. Re:Looking back... by Tatarize · · Score: 4, Funny

      ech tee tee pee colon slash org dot slash dot dot org - Not as cool to say.

      There is a reason for the double slash. The double slash says it's the traditional format. The single slash signifies the domain name extension should go first. In the new-Berners-Lee format...

      For example.

      http://slashdot.org
      http:/org.slashdot

      Should both be allowed addresses. They aren't. But, because he did a double slash in the beginning we could actually flip the extention order and drop the slash and it wouldn't be confused with the original format. See, Sir Tim is such a foward thinker he added a worthless slash to save the day years later!

      --

      It is no longer uncommon to be uncommon.
    3. Re:Looking back... by timeOday · · Score: 5, Insightful

      Left or right isn't the problem; the problem with URLs is that they're inconsistent. Reading from left to right, the hostname goes from most specific to most general, while the rest of the path is just the opposite.

    4. Re:Looking back... by mattkinabrewmindspri · · Score: 4, Insightful

      -like the way most Americans write dates. Most Americans write in this order: March 25, 2006 or: 03-25-2006 The second one is more specific, while the third is less specific. It would make more sense to write 2006-03-26, so the numbers get more specific, or 26-03-2006, like other countries, so the numbers get less specific.

  4. But how could you make a jingle out of ... by Ungrounded+Lightning · · Score: 5, Insightful

    Sir Tim Berners-Lee ... says he got domain names backwards in web addresses all those years ago.

    But how could you make an advertising jingle out of

    "com dot expediAAAAAAHHH!"

    --
    Bantam Dominique roosters crow a four-note song. Once you've heard it as "Happy BIRTHday" you can't NOT hear it that way
    1. Re:But how could you make a jingle out of ... by BluBrick · · Score: 5, Funny

      Perhaps so, but these guys might be able to sell their domain name for a big ol' crapload of research funding!

      --
      Ahh - My eye!
      The doctor said I'm not supposed to get Slashdot in it!
    2. Re:But how could you make a jingle out of ... by Archon-X · · Score: 4, Funny

      Glad you brought that up, I've been waiting for a semi-relevant posting for years now to ask the following question: Am I the only one that reads '.org' as 'orgy'?

      It's fun, it's naughty! Catholic.org! Nun.org! Starving-Panda.org! ..no, wait.

  5. Re:JACK ASS by oberondarksoul · · Score: 5, Funny

    Be nice; he invented the medium you're using to flame him... ;)

    --
    And tomorrow the stock exchange will be the human race
  6. TLDs by user24 · · Score: 4, Insightful

    "I don't think we've gained anything from the .biz or .info domains - only that a few companies have benefited financially"

    at least someone realises this.

    If i had my way i'd redo the whole domain system; the distinctions between TLDs are totally irrelevent these days.
    That or enforce the distinctions, so that only ISPs can have .nets, only charities .orgs, etc etc.

  7. Re:JACK ASS by Anonymous Coward · · Score: 5, Insightful

    Unlike some people, Sir Tim Berners-Lee actually achieved something (you know that thing they call the World Wide Web) that paved the way for him to be knighted by the Queen. Think of that the next time someone says "Yes, sir" to a manager.

  8. A true Brit. by jd · · Score: 4, Informative
    JANET (the Joint Academic Network) used to use X.25, which used reverse domain names, if I recall correctly. It also used HORRIBLE addressing notation. Essex University's DEC 10 (which ran the first ever massively multi-user adventure game, or rather three of them) had an address of A2206411411. (Yes, I really do remember that.)


    So the idea that he started off having trouble with the Berkeley naming convention doesn't surprise me at all.


    (I'd prefer a more heirarchical system, myself, where an organization can ONLY have one domain name and have all their actual addresses inside of that. It would make the namespace a lot less cluttered and would reduce trademark abuses. On the other hand, names would be a lot longer. However, if you're using a search engine, a portal or bookmarks most of the time anyway, that's no big deal.)

    --
    It's a small world and it smells funny; I'd buy another if it wasn't for the money; Take back what I paid (SoM)
    1. Re:A true Brit. by Anonymous Coward · · Score: 5, Funny
      If you're going to use bookmarks, portals and search engines anyway, why not leverage them fully and make all names/identifiers collision-free cryptographic names. Trademark problem: solved permanently.


      In fact, every machine on the internet could be given a unique 32 bit number. Then you could connect to it using that number as the name. That would be awesome!
  9. Re:JACK ASS by tha_mink · · Score: 4, Funny

    Be nice; he invented the medium you're using to flame him... ;)

    Doesn't make Henry Ford a good driver...

    --
    You'll have that sometimes...
  10. Won't work by rs79 · · Score: 4, Insightful

    ""I don't think we've gained anything from the .biz or .info domains - only that a few companies have benefited financially"

    at least someone realises this.

    If i had my way i'd redo the whole domain system; the distinctions between TLDs are totally irrelevent these days.
    That or enforce the distinctions, so that only ISPs can have .nets, only charities .orgs, etc etc."


    The purpose of a domain name is to make it easy for poeple. Computers don't care, they use IP addresses and the DNS is simpy a way to make easy to rememeber names that are automatically converted to IP addresses by software.

    There is no taxonomy or more correctly, ontology, behind domain names. They're arbitrary strings of characters. There is no meaning whatsoever in the TLD, that's sad articfact of the way things were; they should not ideally have any meaning.

    NSI under the original Internic cooperative agreement tried for many years to enforce the .NET rule of "internet infrastructural addresses only". It was impossible. Poeple who wanted to cheat the system always found ways and the harder NSI made it the more difficult it was for legitimate users to get .NET addresses.

    TLDS should be meaningful, but arbitrary. And pretending any sort of classification system can me made out of it belies two decades of expereince with the way we name computers on the network.

    Sir Tim may be a Sir but he's dead wrong about this expansion of tld space. Would you find it easier to remember (and yes, there are times you'll rememeber and type in, instead of looking something up in a search engine) company.biz or perhaps company.info because that was available when perhapes the only thing available in .COM was "i-my-e-companynicheproduct.com"?

    Typically the internet solves problems of scarcity (.com names) by creating new resources, not by regulating old ones.

    --
    Need Mercedes parts ?
  11. 'Duh' Browser security by cpeikert · · Score: 4, Interesting

    Best comment in the interview:

    "Most browsers have certificates set up and secure connections, but the browser view only shows a padlock - it doesn't tell you who owns the certificate."

    I still can't believe that, to this very day, there is no major browser that displays the right information about a certificate by default! This is the whole point of a certificate: it tells you that paypal.com actually belongs to a real-world entity named "PayPal Inc."

    At the very least, when connected via SSL to a site with a valid cert, the browser address bar should have an extra line that names the real-world entity. A yellow padlock and location bar tell you nothing about who you're really talking to. You shouldn't have to manually examine the certificate to find out this information.

    Does anyone have any idea why even Firefox, with all its other great usability and security innovations, still gets this basic thing wrong??

    1. Re:'Duh' Browser security by Jerf · · Score: 4, Insightful

      We made a mistake back in the day. Certificates are serving two purposes: One is to encrypt the data, one is to verify identity.

      This makes it a major pain when you just want to encrypt data without claiming to be anyone in particular, since you have to jump through a lot of hoops both on server and client side to get it working. The browser gets bitchy about a certificate that isn't signed by any of its roots, even though it may very well be the case that nobody cares.

      If we clearly thought about these two aspects, and separated them, it would become clear that A: we need a better way to just say "secure the damn connection" without claiming to be anybody and B: When a site is claiming to be somebody, it hardly makes sense to not show the claim clearly to the user. But since the concepts are all mushed up, you get a lock icon that sort of covers half the situation, mostly, and few people really realize there's a problem.

    2. Re:'Duh' Browser security by Beryllium+Sphere(tm) · · Score: 4, Insightful

      >why would you send it to a random stranger? Verification of the recipient's identity is crucial.

      That's a good explanation and it's accurate. It does have a hidden assumption though.

      A lot of security analysis takes as an axiom that the threat is an intelligent and determined adversary who will crawl in through any weakness. That axiom may seem self-evident because of infosec's military heritage: if your opponent is willing to hire Alan Turing and invent the digital computer in order to read your ciphertext, you daren't leave any chink in your armor.

      If you're a civilian and willing to gamble that you'll only be a random target and that your opponents will always go for the softest targets, then you might decide on a self-signed certificate. You might believe that sniffing Internet traffic is so much easier than running a man-in-the-middle attack that you could just take your chances on MiTM.

      You'd be wrong in today's environment, though. Phishing means you really have to worry about who a public key really belongs to. Not that certs are helping very much.

      Quite a few people are proposing a compromise trust model like ssh has, where the browser UI would change so as to warn you when you're about to encrypt to an unexpected public key.

  12. well, he got it wrong again by blair1q · · Score: 4, Interesting

    get rid of the dot notation entirely if you're not going to admit you just used the domain naming system that pre-existed the web

    if the server name isn't going to be the name of a server, then you can do this:

    http://uk/org/bcs/members

    and now everything is a hierarchical pathname that is resolved to a fqdn internally and nobody needs to worry that bcs.org.uk is a node on the network and members is a service on that node...

    add it to the pile of big-woops! ideas along with ken thompson's anally elided 'e' in "creat()"...

  13. A sad case of marketing anti-genius by KingSkippus · · Score: 4, Interesting

    The following story is true, though extraordinarily sad.

    At the company where I used to work, they registered all TLDs for their name. We had .com, .net, .org, .biz, etc.

    One day, our chief marketing goober decided that .biz was going to be the next "in" thing on the Internet, and we would be one of the first companies to capitalize on it. So we had all of our business cards chaged, our mailers, our letterhead... everything. We were explicitly told never to use the .com domain name in our business dealings, it was .biz. We, the IT gurus, begged and implored them not to do this, that it would cause more trouble in the end than it was worth, and that the only companies that use .biz are fly-by-night companies that grab the .biz equivalent of famous .com names so that they can rip people off.

    Who do you think they listened to?

    Long story short: Within a few months, after our customers, suppliers, vendors, and lots of other really, really important people started complaining that their e-mails to us were bouncing back and e-mails from us were not being received because spam blockers were automatically assuming that our .biz address either weren't valid, our chief marketing goober decided to "spend more time with his family," our old business cards, letterhead, etc. was dug out, and we were instructed never to use the .biz domain name again.