Slashdot Mirror

← Back to Domains

Domain: meta.net.nz

Stories and comments across the archive that link to meta.net.nz.

Comments · 7

  1. Re:Are we talking... by Architect_sasyr · · Score: 1 · on Computer Designed Car Sets Speed Record

    Well at least there will be less waste than the Avian Transport of yester year... Ref: http://coders.meta.net.nz/~perry/rfc/index-1149.ht ml RFC 1149 http://coders.meta.net.nz/~perry/rfc/index-2549.ht ml RFC 2549, and quicker too.

  2. Re:Are we talking... by Architect_sasyr · · Score: 1 · on Computer Designed Car Sets Speed Record

    Well at least there will be less waste than the Avian Transport of yester year... Ref: http://coders.meta.net.nz/~perry/rfc/index-1149.ht ml RFC 1149 http://coders.meta.net.nz/~perry/rfc/index-2549.ht ml RFC 2549, and quicker too.

  3. My little internet mapping project by Isomer · · Score: 3, Informative · on Mapping the Internet Evolution

    I have my own little internet mapping project ( http://tr.meta.net.nz/ ) which is designed in a similar way (people run traceroute nodes on their machines and information is merged together to provide pretty graphs). I wrote it because people would say "I can't get to this site, can anyone else get to it?" This lets you type in the hostname of a machine and it will take lots of traceroutes from around the Internet and merge them into a graph that you can use to figure out which particular segments of the Internet can/can't access it and where they all get tripped up. Or you can see that you're going via an international route, where as almost everyone else is going across a local exchange point. Also as it has AS# information on it you can determine who's fault it is.

    tr produces a "small" section of the Internet (it doesn't map the entire thing) but it produces it in a way that can be interpreted by anyone savvy in network administration. It's mostly based in NZ (as thats what I care about, and thats where I have contacts where people are happy to run tr nodes) but it does show how the NZ Internet works extremely well, and provides reasonable detail to the rest of the Internet.

    Some interesting examples:
    Microsoft: http://tr.meta.net.nz/output/2005-04-08_20:08_micr osoft.com.png
    Google: http://tr.meta.net.nz/output/2005-05-16_10:14_www. google.com.png
    F root server anycast: http://tr.meta.net.nz/output/2005-05-16_10:16_f.ro ot-servers.net.png

  4. My little internet mapping project by Isomer · · Score: 3, Informative · on Mapping the Internet Evolution

    I have my own little internet mapping project ( http://tr.meta.net.nz/ ) which is designed in a similar way (people run traceroute nodes on their machines and information is merged together to provide pretty graphs). I wrote it because people would say "I can't get to this site, can anyone else get to it?" This lets you type in the hostname of a machine and it will take lots of traceroutes from around the Internet and merge them into a graph that you can use to figure out which particular segments of the Internet can/can't access it and where they all get tripped up. Or you can see that you're going via an international route, where as almost everyone else is going across a local exchange point. Also as it has AS# information on it you can determine who's fault it is.

    tr produces a "small" section of the Internet (it doesn't map the entire thing) but it produces it in a way that can be interpreted by anyone savvy in network administration. It's mostly based in NZ (as thats what I care about, and thats where I have contacts where people are happy to run tr nodes) but it does show how the NZ Internet works extremely well, and provides reasonable detail to the rest of the Internet.

    Some interesting examples:
    Microsoft: http://tr.meta.net.nz/output/2005-04-08_20:08_micr osoft.com.png
    Google: http://tr.meta.net.nz/output/2005-05-16_10:14_www. google.com.png
    F root server anycast: http://tr.meta.net.nz/output/2005-05-16_10:16_f.ro ot-servers.net.png

  5. My little internet mapping project by Isomer · · Score: 3, Informative · on Mapping the Internet Evolution

    I have my own little internet mapping project ( http://tr.meta.net.nz/ ) which is designed in a similar way (people run traceroute nodes on their machines and information is merged together to provide pretty graphs). I wrote it because people would say "I can't get to this site, can anyone else get to it?" This lets you type in the hostname of a machine and it will take lots of traceroutes from around the Internet and merge them into a graph that you can use to figure out which particular segments of the Internet can/can't access it and where they all get tripped up. Or you can see that you're going via an international route, where as almost everyone else is going across a local exchange point. Also as it has AS# information on it you can determine who's fault it is.

    tr produces a "small" section of the Internet (it doesn't map the entire thing) but it produces it in a way that can be interpreted by anyone savvy in network administration. It's mostly based in NZ (as thats what I care about, and thats where I have contacts where people are happy to run tr nodes) but it does show how the NZ Internet works extremely well, and provides reasonable detail to the rest of the Internet.

    Some interesting examples:
    Microsoft: http://tr.meta.net.nz/output/2005-04-08_20:08_micr osoft.com.png
    Google: http://tr.meta.net.nz/output/2005-05-16_10:14_www. google.com.png
    F root server anycast: http://tr.meta.net.nz/output/2005-05-16_10:16_f.ro ot-servers.net.png

  6. My little internet mapping project by Isomer · · Score: 3, Informative · on Mapping the Internet Evolution

    I have my own little internet mapping project ( http://tr.meta.net.nz/ ) which is designed in a similar way (people run traceroute nodes on their machines and information is merged together to provide pretty graphs). I wrote it because people would say "I can't get to this site, can anyone else get to it?" This lets you type in the hostname of a machine and it will take lots of traceroutes from around the Internet and merge them into a graph that you can use to figure out which particular segments of the Internet can/can't access it and where they all get tripped up. Or you can see that you're going via an international route, where as almost everyone else is going across a local exchange point. Also as it has AS# information on it you can determine who's fault it is.

    tr produces a "small" section of the Internet (it doesn't map the entire thing) but it produces it in a way that can be interpreted by anyone savvy in network administration. It's mostly based in NZ (as thats what I care about, and thats where I have contacts where people are happy to run tr nodes) but it does show how the NZ Internet works extremely well, and provides reasonable detail to the rest of the Internet.

    Some interesting examples:
    Microsoft: http://tr.meta.net.nz/output/2005-04-08_20:08_micr osoft.com.png
    Google: http://tr.meta.net.nz/output/2005-05-16_10:14_www. google.com.png
    F root server anycast: http://tr.meta.net.nz/output/2005-05-16_10:16_f.ro ot-servers.net.png

  7. Other 4D games by Isomer · · Score: 1 · on Four-Dimensional Rubik's Cube Craziness
    I wrote a two player web based 4d three-in-a-row game one evening when I was bored.

    I didn't find it particularly hard to play, but some people do. I think it's a good way to practise thinking about things abstractly.

    Anyway, find a friend, and play a few games, see how you do. The rules are slightly different, you play until you fill the board, and the person at the end with the most numbers of three in a row wins.