Late Thursday evening I checked my fimfic notifications. There were... a lot of them. And the first 9 were comments on my stories, all by PaulAsaran, all saying "You can has review!" He spent 9 of his 10 story slots this week on me.
Regidar recently posted a request for links to experimental fics. I decided to just add a bookshelf, Experimental, and list my favorite and my own experimental stories there. (My stories will probably appear first, because I added
That most-peculiar book, The Hitchhiker's Guide to the Galaxy, describes in Fit the Fourth how representatives of the Amalgamated Union of Philosophers, Sages, Luminaries, and other professional thinking persons confronted Deep Thought, the second greatest computer in the universe, when it threatened to find the answer to
3423942 I don't even know how they did it. horse is now a top-level domain, but those other words aren't. And it would be hella expensive to buy all those domains just for a prank.
3424258 Also, I didn't realize you were a thing of something until now, because I haven't watch much of the Doogie thing. I just thought Bad Horse was all oh-gee. (Not that I'm saying you're unoriginal or anything.)
I can only assume the o_o part sealed the deal on your username
SimpleDNS A special PTR-record type is used to store reverse DNS entries. The name of the PTR-record is the IP address with the segments reversed + ".in-addr.arpa".
Wikipedia The original use of the rDNS: network troubleshooting via tools such as traceroute, ping, and the "Received:" trace header field for SMTP e-mail, web sites tracking users (especially on Internet forums), etc.
serverfault Although it's not "nice", but you can enter almost anything (no spaces etc.) in the PTR field. It does not have to be a valid TLD (since valid TLDs are added/removed every now and then, and internal pages such as http://intranet/ would fail, if there was any validity checking implemented in both DNS and rDNS)
Traceroute works by sending successive UDP packets containing a standard ICMP Ping. Packets have a number in their header called 'Time to Live', or TTL. The sender sets that number, and every time a router receives the packet, it knocks one off that number before passing it along. When the number reaches 0, the router that has the packet at that point discards the packet and sends a message back to the sender letting them know that their packet expired. This is how the internet prevents packets from circling endlessly looking for their destination.
The important thing is that that return packet includes the name of the machine where the packet died, and that's what traceroute displays to you. And the machine just supplies that name, there's no one stopping you from having your machine return Traceroute packets claiming to be google.com, except that the DNS system will not send packets addressed to google.com to your machine in the first place.
Anyway, Traceroute doesn't know it's done until the destination machine replies to the Ping with the message that means 'hello, yes, I am the server you're looking for'. In this case, when you traceroute bad.horse, the first IP you get is the one that the public http page is served from--if you put 162.252.205.130 in your address bar, you get the Bad Horse song. If you just ping 162.252.205.130, however, notice that you're getting replies from 162.252.205.157, which is the machine that finishes the song--your plain ping gets invisibly routed through the whole chain to signed.bad.horse. Basically, he's got a DNS A record for bad.horse = 162.252.205.130 and another one for signed.bad.horse = 162.252.205.157. Everything in between is a static route he's set up internally of machines/VMs/whatever that only send out packet expiration messages and don't respond to a plain ping.
That's what it looks like to me, anyway. Someone who's better at networks than me can feel free to correct or clarify.
Haha :V
I've had my eye on you for a whiiile
morleypedals.com/vai-11.jpg
Saw that on Reddit earlier. I doubt you were the one who actually set it up in the first place.
3423942 I don't even know how they did it. horse is now a top-level domain, but those other words aren't. And it would be hella expensive to buy all those domains just for a prank.
Um...could you please explain this to my shit-eating nooblet self?
The Unix Vigilantes are on your trail!
And they'll bring you to justice as soon as they can gather enough parts to make a gun.
That was awesome.
this is the most beautiful thing I have seen since I just watched Rarijack show five minutes ago
3423976 I suspect that you're allowed to provide DNS name info for your own subnet, though you'd think they'd not let you change its domain.
3424258
Also, I didn't realize you were a thing of something until now, because I haven't watch much of the Doogie thing. I just thought Bad Horse was all oh-gee. (Not that I'm saying you're unoriginal or anything.)
I can only assume the o_o part sealed the deal on your username
This is beautiful.
Whoever set this up had a lot of fun.
Note that if you go to bad.horse (just type it into your browser) it will actually play the song.
3424342
Incidentally, if you've never watched Dr. Horrible's Sing-Along Blog, you should; it is wonderful.
This was well worth the time and money that someone spent on this moment of whimsy.
(Router setup, SSL certificate generation, domain name registration of bad.horse, etc.)
3423948
3423976
3423948
3423976
Traceroute works by sending successive UDP packets containing a standard ICMP Ping. Packets have a number in their header called 'Time to Live', or TTL. The sender sets that number, and every time a router receives the packet, it knocks one off that number before passing it along. When the number reaches 0, the router that has the packet at that point discards the packet and sends a message back to the sender letting them know that their packet expired. This is how the internet prevents packets from circling endlessly looking for their destination.
The important thing is that that return packet includes the name of the machine where the packet died, and that's what traceroute displays to you. And the machine just supplies that name, there's no one stopping you from having your machine return Traceroute packets claiming to be google.com, except that the DNS system will not send packets addressed to google.com to your machine in the first place.
Anyway, Traceroute doesn't know it's done until the destination machine replies to the Ping with the message that means 'hello, yes, I am the server you're looking for'. In this case, when you traceroute bad.horse, the first IP you get is the one that the public http page is served from--if you put 162.252.205.130 in your address bar, you get the Bad Horse song. If you just ping 162.252.205.130, however, notice that you're getting replies from 162.252.205.157, which is the machine that finishes the song--your plain ping gets invisibly routed through the whole chain to signed.bad.horse. Basically, he's got a DNS A record for bad.horse = 162.252.205.130 and another one for signed.bad.horse = 162.252.205.157. Everything in between is a static route he's set up internally of machines/VMs/whatever that only send out packet expiration messages and don't respond to a plain ping.
That's what it looks like to me, anyway. Someone who's better at networks than me can feel free to correct or clarify.
3424628
I've heard!
This is one of those things that I need to do but can't bring myself to. It's weird. I probably will see it someday though.
3424815
Agreed.
3423948
Did you actually just suggest that somepony could spend too much time, effort, or money on humor?
I mean, that better be impossible, because I'm definitely going to be fired someday for the lengths I am willing to go for the tiniest joke.
Man, there are a lot of nerd words here I don't get it.
apparently it flips you between 2 ips in milp.iphouse.net